OpenID Connect request and response mapping
The OAuth and Open ID Connect authorization flows in IBM Security Verify consists of request mapping and response mapping.
The OAuth and Open ID Connect authorization flow in IBM Security Verify consists of the
following steps:
- Authentication: Checks for an authenticated session in the browser and if the user did not authenticate, redirects the user for authentication.
- Request mapping: Modifies the authorization request for specific request parameters. This mapping is only supported for the authorize endpoint.
- User authorization: Checks whether the user is entitled to access the application.
- User consent: Obtains user authorization to share data and perform actions on their behalf.
- Attribute mapping: Enriches the authorization grant with more computed and mapped values. These values are included in the ID token, user info response and introspection response.
- Token generation: Builds the token, as requested, based on the
response_type
in the authorization request. - Response mapping: Modifies the response to add more headers and parameters. This mapping is only supported for the authorize and token endpoints.
Request mapping
The following steps are done on the applications Sign-on tab.- Under Endpoint configuration, click the edit icon for the Authorize endpoint.
- Under Request mapping, click Edit on the specific request parameter row . For example, if you want to modify the user consent request or adding more context for the page, click the Edit on the "Consent request" row.
- Author and test the custom rule.
- Click OK. The application is not yet saved, so the changes are not persisted.
- Click OK to return to the application Sign-on page.
- Click Save on the application page to persist the changes.
Note: Custom HTTP headers are not available in request mapping for the authorize
endpoint.
Response mapping
The following steps are done on the applications Sign-on tab.- Under Endpoint configuration, click the edit icon for the Authorize or the Token endpoint.
- Under Response mapping, click Add response mapping rule.
- Choose the type of target parameter. For example, if Header is chosen, the computed value is added to the HTTP response header.
- Enter a name for the target parameter.
- Click the Edit icon to add or edit a custom rule. See Attribute functions. All domain objects that are listed in this page are available.
- Click OK. The application is not yet saved, so the changes are not persisted.
- Click OK to return to the application Sign-on page.
- Click Save on the application page to persist the changes.