<iframe src="https://www.googletagmanager.com/ns.html?id=GTM-M74D8PB" height="0" width="0" style="display:none;visibility:hidden">
Loading
Skip to NavigationSkip to Main Content
0D54z0000A1AhTjCQKOkta Identity EngineIdentity GovernanceAnswered2025-04-12T09:08:12.000Z2024-03-08T18:58:47.000Z2024-03-19T18:36:19.000Z
  • TimL.58332 (Workflows)

    @oa4db (oa4db)​ - The solution is in the error message. The client app (where you are obtaining the client id/secret) typically has a field for specifying valid redirect URI's. These are ones it considers to be an authorized location to send the redirect data back to. If location where you are originating the request to setup a connection (A client such as Workflows, Postman, etc) doesn't have it's redirect URI specified then the client app won't send back the User Consent webpage. So you won't be able to perform the consent for an Authorization Code grant.

    Expand Post
    Selected as Best
  • TimL.58332 (Workflows)

    @oa4db (oa4db)​ - The solution is in the error message. The client app (where you are obtaining the client id/secret) typically has a field for specifying valid redirect URI's. These are ones it considers to be an authorized location to send the redirect data back to. If location where you are originating the request to setup a connection (A client such as Workflows, Postman, etc) doesn't have it's redirect URI specified then the client app won't send back the User Consent webpage. So you won't be able to perform the consent for an Authorization Code grant.

    Expand Post
    Selected as Best
This question is closed.
Loading
400 Bad Request Your request resulted in an error. The 'redirect_uri' parameter must be a Login redirect URI in the client app settings: