Oauth2
(Replacing message template with parser tag)
(Updated Edited template to July 12, 2025.)
Line 21: Line 21:
'''Please note that even though Oauth2 is standard, the naming conventions of all parameters may differ - these names worked using an Identity Server 4.'''
'''Please note that even though Oauth2 is standard, the naming conventions of all parameters may differ - these names worked using an Identity Server 4.'''
[[Category:Authentication]]
[[Category:Authentication]]
{{Edited|July|12|2024}}
{{Edited|July|12|2025}}

Revision as of 05:59, 20 January 2025

This page was created by Henrik on 2019-03-10. Last edited by Stephanie@mdriven.net on 2025-02-14.

Client Credentials Grant Flow

Server-to-server authentication using Oauth2 and the Client credentials grant flow may be supported using these steps. Other flows may also be supported in a similar flow. User-authentication using Oauth2 and OpendId is described here.

1. Set up the call to obtain the "token" using the client secret, storing the result in transient classes as shown on the right:

GetTokenOauth2.PNG

TokenModel.PNG

2. Set up a server-side ViewModel to refresh the token before expiry, using criterias (as an example) as shown below.

OauthSSCriteria.PNG

2. Pass the "token" in all subsequent calls:

Oauth2Call.PNG


Please note that even though Oauth2 is standard, the naming conventions of all parameters may differ - these names worked using an Identity Server 4.