Oauth2
    No edit summary
    No edit summary
     
    (11 intermediate revisions by 4 users not shown)
    Line 1: Line 1:
    '''Server to server authentication''' using Oauth2 and the [https://tools.ietf.org/html/rfc6749#section-4.4 Client credentials grant flow] may be supported using these steps. Other flows may of course also be supported in a similar flow. User-authentication using Oauth2 and OpendId is described [[Openid] here]
    <message>Write the content here to display this box</message>
    ===Client Credentials Grant Flow===


    1. Set up the call to obtain the "token" using the client secret, storing the result in transient classes as shown to the right
    '''Server-to-server authentication''' using Oauth2 and the [https://tools.ietf.org/html/rfc6749#section-4.4 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 [[Documentation:Openid AzureAD|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:


    [[File:GetTokenOauth2.PNG]]
    [[File:GetTokenOauth2.PNG]]
    Line 7: Line 10:
    [[File:TokenModel.PNG|thumb|right]]
    [[File:TokenModel.PNG|thumb|right]]


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


    [[File:OauthSSCriteria.PNG]]
    [[File:OauthSSCriteria.PNG]]


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


    [[File:Oauth2Call.PNG]]
    [[File: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.'''
    '''Please note that eventough Oauth2 is a standard, the naming conventions of all parameters may differ, these names worked using a Indentity Server 4'''
    [[Category:Authentication]]
    {{Edited|July|12|2025}}

    Latest revision as of 05:30, 14 February 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.

    Retrieved from "https://learn.mdriven.net/index.php?title=Documentation:Oauth2&oldid=26455"

    © MDRIVEN . All Rights Reserved

    API Docs
    MDriven World | Portal | Blog | YouTube | StackOverflow | Facebook

    © MDRIVEN . All Rights Reserved