Rate this page

Followup Responses

When the auth UI makes a response to a followup URI, the request is handled by the OAuth service’s authorization endpoint. At this point, the Data Governance Broker’s policy engine will examine the state of the authentication flow and determine the response returned, which may either be a flow URI response or a continue redirect response. In either case, the auth UI should respond by making a GET request for the URI contained in the followup response, which will transition the authentication flow to the next state.

Flow URI response

A flow URI response is returned when the Broker determines that the auth UI must now transition to a different authentication flow. For example, after the login flow is satisfied, a transition may be made to the second factor flow or the consent flow.

Field Type Provided? Description
flow_uri string always The URI of the next flow to request. Requesting this URI using GET will load the next flow.

An example flow URI response:

{
  "flow_uri": "https://example.com/authentication/approve/ARH5F9B..."
}

Continue Redirect URI response

A continue redirect URI response is returned when the Broker determines that there is no other authentication flow to process. When the auth UI requests this URI, the end user’s browser will be redirected back to the OAuth 2 client that initiated the authentication request. The redirect response received by the client will be structured according to the OAuth 2 grant type used by the client.

Field Type Provided? Description
continue_redirect_uri string always The final URI to request from the auth API. Requesting this URI using GET will trigger a redirect back to the client that initiated the authentication process.

An example continue redirect URI response:

{
  "continue_redirect_uri": "https://example.com/oauth/authorize?final_state=ARH5F9B..."
}