Skip to content

Claims Gathering Endpoint#

Overview#

The Claims Gathering endpoint is part of the User-Managed Access (UMA) authorization flow. It is used when the Authorization Server determines that the claims already presented by the requesting party are not sufficient to satisfy the authorization policies protecting a resource.

When additional claims are required, Janssen Server returns a response instructing the client to redirect the requesting party to the Claims Gathering endpoint. The client redirects the requesting party to the endpoint together with the required parameters, including client_id, the current permission ticket, and claims_redirect_uri.

After the requested claims have been collected, Janssen Server redirects the requesting party to the registered claims_redirect_uri with a new permission ticket. The client then presents the new permission ticket to the token endpoint for authorization assessment. The token endpoint returns an RPT or an UMA error based on the authorization result.

If the client also presents an existing RPT, Janssen Server may upgrade it. An RPT should be considered upgraded only when the token response contains "upgraded": true.

For protocol details, see the UMA 2.0 Grant specification:

Configure Claims Gathering#

Claims Gathering is driven by the UMA authorization policies configured for a protected resource and the associated Claims Gathering script.

Register the Claims Gathering Redirect URI#

The Claims Gathering redirect URI is configured as part of the client registration. In Janssen Server, set the claimRedirectUris property on the client to specify authorized target URIs for the Claims Gathering flow. You can configure this via Jans TUI or Jans CLI:

For instructions on configuring client properties using the Jans TUI, see Client Management - TUI.

For instructions on configuring client properties using the Jans CLI, see Client Management - Jans CLI.