Skip to main content
Version: 4.42

Configure the redirect URIs

info

Redirect URI configuration for internal integrations is available from version 4.42.3.

Overview​

Before an external application can complete the Sign API OAuth2 authorization code flow, the Redtrust administrator must register that application's redirect URIs. Redtrust only redirects the user to addresses that are authorized in advance for the service, so the authorization flow rejects any redirect_uri that doesn't match a registered URI.

You manage this configuration from the admin console, as shown below. Each integration represents an internal Redtrust service (for example, Sign service) and includes its client ID and the list of accepted redirect URIs.

note

To manage internal integrations, you need the Services permission (see Role permissions settings).

Sign service only appears if your installation is licensed for the Signtrust module. If no service has an active license, the section shows a message instead of the table.

Create an internal integration​

  1. In the admin console, go to System > Services > Internal integrations.
  2. Select New internal integration.
  3. Choose the service from the list of available services. The Client ID is set automatically and can't be changed.
  4. Add one or more redirect URIs. Each URI must be an absolute address that Redtrust can redirect the user to after authentication.
  5. Save your changes.

The external application can now use any of the registered URIs as the redirect_uri in the OAuth2 flow.

note

To change the URIs of an existing integration, open it from the table, add or remove URIs as needed, and save your changes. An integration must always keep at least one redirect URI; to remove them all, delete the integration.

Next steps​

Once the redirect URIs are registered, see the OAuth2 authorization code flow to complete authentication and integrate the Sign API.

Was this page helpful?