Appian Community
Site
Search
Sign In/Register
Site
Search
User
DISCUSS
LEARN
SUCCESS
SUPPORT
Documentation
AppMarket
More
Cancel
I'm looking for ...
State
Not Answered
Replies
4 replies
Subscribers
5 subscribers
Views
2741 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
Integrations
Hi Team, Regarding access to Google APIs(ex. Google Calendar). Curre
riang
over 8 years ago
Hi Team,
Regarding access to Google APIs(ex. Google Calendar). Currently Google is using OAuth 2.0. Before when using OAuth 1.0, you need to input Consumer Key, and Consumer Secret to be able to use Create Event Smart Service. This time in OAuth 2.0, ClientId and Client Secret. In OAuth 2.0, you need to setup a credential to access Google API (like Google Calendar API). Once setup, you can download that in the form of .json file.
Now, the way OAuth 2 works is if you are first time to access a Google API it asks you to authorize access/permissions via Consent Screen(Google web page). Once you click the button authorize, a StoredCredential will be saved to your machine. That file allows you to bypass Authorization / Consent Screen since you have authorized it already the first time you set it up.
Is there a way in Appian that you can direct(runtime proces not using a weblink or safelink) a user to a Google Consent Screen to authorize access to the A...
OriginalPostID-196704
OriginalPostID-196704
Discussion posts and replies are publicly visible
Parents
0
riang
over 8 years ago
...PI? and then on that page, it will return to appian if the user allowed/permit access to the API. Once it allows access, a StoredCredential file will be stored on the server and will be read everytime the user accesses Google API.
This is the way Google OAuth2.0 is implementing it's security using OAuth Consent Screen.
Thanks in advance!
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Reply
0
riang
over 8 years ago
...PI? and then on that page, it will return to appian if the user allowed/permit access to the API. Once it allows access, a StoredCredential file will be stored on the server and will be read everytime the user accesses Google API.
This is the way Google OAuth2.0 is implementing it's security using OAuth Consent Screen.
Thanks in advance!
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Children
No Data