Hi , We are planning to use " authorization grant flow via a back-end API call ". Could you please let me know the process to get the access token and refresh token after we create API-only user with appropriate permissions ? This is to pull data from lithium community sites and display on some of our other sites. An earliest response will help a lot ! Thanks,Hari

Hi Hari329 the "Authorization Grant" flow is interactive and therefore not suitable for a server to server integration. You could of corse log in manually with the "API user" via the browser and obtain an access and refresh token, and then use these directly, but I don't think this would be suitable for a back-end integration. What I suggest for the time being is to see whether you can use rest V1 in that scenario, for the time being. Thanks,

To clarify my above response, you could also approach this by coding an administrative interface which allows an authorized admin user to link your application via the interactive flow (using the api only account) and then persists the tokens that will be used for the subsequent calls. This would also allow to refresh the tokens if they become invalid and for some reason it's not possible to get a new one via a refresh token etc...

Hi Hari329 I think this is described in the documentation I have linked. Essentially, you have 24 hours to use your refresh token to obtain a new refresh/access token pair. If more time passes, you may need to re-do the initial authentication log-in flow. Re the administrative interface part: I am referring to the "manual" login part - this could be done via an appropriate UI (an administrative interface to obtain valid tokens) rather than completely manually. Cheers,

Hi Hari329 further to the above. The documentation mentions the following Using the authorization grant flow via a back-end API call The authorization grant flow assumes that a web browser is involved during authentication. If you want to use a back-end API call for OAuth, create an API-only user with appropriate permissions to make the API calls. This API-only user must login once through the community using the authorization flow to receive access and refresh tokens. From there on subsequent authenticated, backend API calls can be made using the tokens. What that means is, even if the user will be used for back end calls, they will still need to go trough the standard OAuth interactive exchange for the first login, to make sure that you can get a valid access token and refresh token for that user. The below diagram (from the KB page) depicts the interactive exchange (which is the same used for normal, non API users) At the end of the process (which can be initiated with any suitable HTTP client, manually) you will have obained an access token and a refresh token and you can then store them in your application for subsequent calls. SuzieH - it looks like our KB page may need some more detail to avoid confusion around this manual step required for backend users. Is that something you can help with? Thanks,

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.

Using the authorization grant flow via a back-end API call

PaoloT
Lithium Alumni (Retired)
10 years ago
Hi Hari329

the "Authorization Grant" flow is interactive and therefore not suitable for a server to server integration. You could of corse log in manually with the "API user" via the browser and obtain an access and refresh token, and then use these directly, but I don't think this would be suitable for a back-end integration.

What I suggest for the time being is to see whether you can use rest V1 in that scenario, for the time being.

Thanks,
- PaoloT
  Lithium Alumni (Retired)
  10 years ago
  To clarify my above response, you could also approach this by coding an administrative interface which allows an authorized admin user to link your application via the interactive flow (using the api only account) and then persists the tokens that will be used for the subsequent calls. This would also allow to refresh the tokens if they become invalid and for some reason it's not possible to get a new one via a refresh token etc...
  - Hari329
    Adept
    10 years ago
    Hi Paolo Tagliaferri,
    
    Thanks for the information. Below are the steps we planned :
    
    1.Create API user
    2.Log in manually with the "API user" to our lithium communities site and obtain an access and refresh token. Could you please help me to understand the steps involved in obtaining access and refresh key after log in ?
    3.Once we get the access and refresh key with manual log in process , we are planning to store it in our system to use whenever we are calling lithium communities using REST API to get the data
    
    Do you see any issues with above process ?
    
    And also could you please elaborate on administrative interface process you mentioned below ?
    
    Thanks a lot for your support,
    Hari

Forum Discussion

Using the authorization grant flow via a back-end API call

Related Content

Aurora: Add co-authors to blog posts

503 - Service unavailable back-end server is at capacity

Aurora: Remove co-authors from blog posts

How to Use Atlas

Help Us Help You!

Recent Discussions

Boosting a User

Google Tag Manager and Google Analytics Setup in Aurora platform

In Aurora, add additional <script> and <meta> tags

Incremental data for attachments in messages and replies

Incremental data for users data