Passing parameters when using OAuth2ClientFilter ?

Tagged: ,

This topic has 4 replies, 2 voices, and was last updated 5 years, 8 months ago by kfriesen-ww.

  • Author
    Posts
  • #7011
     kfriesen-ww
    Participant

    Hi,

    Is it possible to add parameters to the authorization endpoint URL when using OAuth2ClientFilter ?

    My OAuth 2.0 Client is configured at a realm level so need to add &realm=XX to the url.

    #7075

    Yes, when you provide the authorizeEndpoint URI value in config, you can provide query string elements.
    We’re just appending the OAuth 2.0 required additional elements (response_type, client_id, state, …).

    Something like this should be OK:

    
        {
            "type": "Issuer",
            "config": {
              "authorizeEndpoint": "https://openam.example.com/openam/oauth2/authorize?realm=employee",
              "tokenEndpoint": "https://openam.example.com/openam/oauth2/token?realm=employee"
            }
        }
    
    #7176
     kfriesen-ww
    Participant

    Thanks, I was using
    “wellKnownConfiguration”:”http://openam.example.com/openam/.well-known/openid-configuration”,
    Which doesn’t appear to be modifiable via parameters.

    #7177

    Seems that you can add a realm query string element in this URL as well.
    See https://backstage.forgerock.com/#!/docs/openam/13/admin-guide#configure-openid-connect-discovery (end of section)

    #7185
     kfriesen-ww
    Participant

    Yes, I was trying to use that approach but authorization endpoint wasn’t changing.

Viewing 5 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic.

©2021 ForgeRock - we provide an identity and access platform to secure every online relationship for the enterprise market, educational sector and even entire countries. Click to view our privacy policy and terms of use.

Log in with your credentials

Forgot your details?