About the RealMe OIDC Messaging Flow

The key steps to simulating the OIDC messaging flow in MTS are below. Details of required parameters and expected responses can be found here.

1. The OIDC Relying Party (RP) redirects the user to the RealMe OIDC Authentication Endpoint via an authentication request.
• You can submit the content of the OIDC authentication request here or send a request directly from your browser by sending your authentication request to the MTS authorization_endpoint (refer table below).
• If your OIDC authentication request does not pass validation, the relevant error messages are provided to assist you in resolving the error, so you can try again.
2. Once your OIDC authentication request successfully passes validation you are redirected to an outcome page, where you can initiate an OIDC authorisation code response which is returned to your redirect endpoint.
3. On receiving a successful authentication response, the relying party can invoke the RealMe Token Endpoint.
4. Once the OIDC token request has been validated, RealMe returns the response:
   • A successful response will include an ID Token.
   • An unsuccessful response will return an error.

MTS Endpoints