OIDC Messaging Test Site

The aim of this site is to provide integrators with a sandbox environment to component test the OIDC authentication flow including responses from RealMe. Specifically, the website provides the ability to:

• integrate and configure a new or existing relying party including validation of the relying party redirect URI(s)
• validate an OIDC authentication request
• submit an OIDC authentication request, followed by the generation of a:
  • successful authentication response or
  • a non-successful authentication response
• send an OIDC Token request, followed by the generation of a:
  • successful token response, including an ID token with dummy data or
  • unsuccessful token response (if the request is invalid for any reason)

The RealMe developers website describes the sending of OIDC messages to and from RealMe. The OIDC messaging is designed to adhere to the base Open ID Connect specification. In doing so, it aims to cater for a broad range of OIDC compliant products.

Messages from the OIDC Relying Party to RealMe

The Messaging Test Site accepts messages entered as either:

• developer input via a form - this allows for interim diagnosis of the authentication request. If validation is successful, further options to test success / failure scenarios are available.
• parameters to the Messaging Test Site OIDC endpoints - this allows the automation of message validation and the return of success / failure responses.

After a successful validation of the authentication request, the Messaging Test Site provides the option to select a success or failure OIDC authentication response which is returned to your service to consume. A successful authentication response will return an authorisation token to the relying party to allow the submission of an OIDC token request. In Production, it is the responsibility of your service to record any failure and associated error response and present it for fault analysis.