1. Create certificates for the online service
For a SAML POST binding integration, a valid certificate is required for signing and encryption. Generally an additional certificate is not required for a subsequent online service for the same business context.
The certificates must meet the RealMe certificate requirements. The certificates produced must be signed by a RealMe compatible trusted Certificate Authority and must comply with the RealMe certificate naming convention.
It is also expected that the online service will have an additional certificate to support https webpage content.
2. Import the RealMe IdP metadata file
Import the RealMe login service SAML v2.0 metadata file and create an association with the appropriate RealMe login service environment.
Download the required ITE or Production metadata file:
ITE login service IdP metadata [ZIP, 2.2 KB]
Production login service IdP metadata [ZIP, 2.4 KB]
3. Export the online service SP metadata file
Export the organisation’s SP SAML v2.0 metadata file from the SAML v2.0 component. The key components to check for compliance with RealMe metadata requirements are:
- EntityID
- Endpoints (Attribute Consumer Service)
- Public X.509 cert
- Organisation info and Contact info.
4. Complete an online integration request
For an integration using POST binding:
- Log in to access the online configuration tool - you should have received an invitation email from the RealMe integration team or your project manager.
- Provide the required configuration details - this needs your organisation's SP metadata file, co-branding logo and provision of other initial configuration parameters.
For an integration using Artifact binding:
1. Create certificates for the online service
For a SAML POST binding integration, a valid certificate is required for signing and encryption. Generally an additional certificate is not required for a subsequent online service for the same business context.
The certificates must meet the RealMe certificate requirements. The certificates produced must be signed by a RealMe compatible trusted Certificate Authority and must comply with the RealMe certificate naming convention.
It is also expected that the online service will have an additional certificate to support https webpage content.
2. Import the RealMe IdP metadata file
Import the RealMe assertion service SAML v2.0 metadata file and create an association with the appropriate RealMe assertion service environment.
Download the required ITE or Production metadata file:
ITE assertion service IdP metadata [ZIP, 2.3 KB]
Production assertion service IdP metadata [ZIP, 2.4 KB]
3. Export the online service SP metadata file
Export the organisation’s SP SAML v2.0 metadata file from the SAML v2.0 component. The key components to check for compliance with RealMe metadata requirements are:
- EntityID
- Endpoints (Attribute Consumer Service)
- Public X.509 cert
- Organisation info and Contact info.
4. Complete an online integration request
For an integration using POST binding:
- Log in to access the online configuration tool - you should have received an invitation email from the RealMe integration team or your project manager.
- Provide the required configuration details - this needs your organisation's SP metadata file, co-branding logo and provision of other initial configuration parameters.