OAuth 2.0 code grant authentication

RE: OAuth 2.0 code grant authentication

girikumard — Mon, 31 May 2021 07:54:26 GMT

Thank you. Reducing the expiry might not work as user could click multiple saves with in that expiry.

Other option - deactivate access token once it is used sounds good if it is possible. will check with AD team

RE: OAuth 2.0 code grant authentication

jagadeesh — Mon, 31 May 2021 07:50:40 GMT

I think this can be managed at Azure AD itself. Reduce the expiry time or deactivate access token once it is used. Try checking with AD team

RE: OAuth 2.0 code grant authentication

girikumard — Mon, 31 May 2021 06:50:58 GMT

okay.

My actual use case is - I need to authorize the user against Azure AD every time he click on a save button. I am able to authorize for the first time using by a connected system using OAuth 2.0 Authorization Code Grant by receiving an access-token and this access token has an expiry of 15 mins. So all the sub-sequent integration calls are getting authenticated for next 15 mins but I want to restrict it and force the user to re-authenticate again via the connected system

RE: OAuth 2.0 code grant authentication

jagadeesh — Mon, 31 May 2021 06:35:43 GMT

No. I didn't get a solution to get connected system output into variable. We are able to overcome this issue by configuring Azure AD to generate only one token rather than 2 tokens.

RE: OAuth 2.0 code grant authentication

girikumard — Mon, 31 May 2021 06:21:46 GMT

Hello Jagadeesh !

Have u found any solution to your above questions ?

I also need to extract connected system response into a variable. Please do let me know if you have a solution ? TIA

RE: OAuth 2.0 code grant authentication

vamsi krishna — Thu, 20 May 2021 06:31:55 GMT

Hi Jagadeesh,

As mentioned in the Integration object designer for the third option,

Default headers will be added to the request automatically. Add headers here to override or extend the default headers. Tip: Test the request to see which headers are being added before adding your own.