Forum Discussion
14 Replies
- SuzieH10 years agoKhoros Alumni (Retired)
PaoloT and Hari329 I added more detail to the section in the OAuth 2.0 documentation describing how to use the API user for back-end calls with OAuth 2.0.
- Hari32910 years agoAdept
Hi ,
Thanks a lot for clarifications and updating documentation. Below is summary of our understanding :
- Obtaining access and refresh key is one time process which can be achieved by manual log in process.
- Once we obtain these keys using this manual log in process , refresh key can be used for subsequent calls for retrieving data as refresh key will never expire.
Please correct me if any one if above statement is wrong.
I have tried to obtain access and refresh tokens in below way :
- Accessed our community site
- Loged in using Sign In option available
- Used my credentials which were granted with API-only permissions to sign in. Below is screenshot after sign in :
- I couldn’t see any option/link to retrieve access and refresh tokens.
Could you please correct me If I am doing wrong process here ? And also please point me from where I can request for access and refresh token.
And also as per documentation (Request authorization section of - http://community.lithium.com/t5/Community-API-v2/OAuth-2-0-authorization-grant-flow/ta-p/138402#getAuthorizationcode), I have tried below process to retrieve authorization code :
But seeing below error :
Its mentioned that he redirect_uri used in the authorization request must match the callback URL defined for the community. Who will be providing this ?
- eurcew10 years agoContributor
I'm experiencing pretty much the same issue with a similar error page but a slightly different code.
I submit this
An Unexpected Error has occurred. - SAS Support Communities
- Your request failed. Please contact your system administrator and provide the date and time you received the error and this Exception ID: 3336769F.
Click your browser's Back button to continue.
- Your request failed. Please contact your system administrator and provide the date and time you received the error and this Exception ID: 3336769F.
- AdamN10 years agoKhoros Oracle
For anyone experiencing the "An Unexpected Error has occurred", please double check that your query string values are URL encoded. client_id and redirect_uri both contain characters that need to be encoded.
If you’re testing outside of a coding environment, this tool might be handy:
Related Content
- 2 years ago
- 5 years ago
- 4 years ago