Once you've set up your SAML component, you can test it against the RealMe® Message Testing Service (MTS) - there are separate versions for login service and assertion service. The primary aim of MTS is to provide developers and integrators with the ability to test the sending of a SAML v2.0 AuthnRequest to the RealMe service and receiving a SAML v2.0 response from the RealMe service. MTS is also required to test exception handling.
As well as providing the functionality to try out SAML requests and responses from your system test environment, the Message Testing Service website provides information and instructions for its use. The website [new feature] also contains the self-signed certificates and sample metadata required for the initial configuration.
Download the Message Testing Service bundle [ZIP, 28 KB] - it contains everything you need for a POST binding (or Artifact binding) Message Testing Service for the RealMe login service or RealMe assertion service. To make this easy, the MTS bundle includes self-signed certificates that you can use. For later integrations, you will need to meet the certificate requirements using one of the specified CAs.
If you're incorporating a SAML products or code libraries or perhaps even considering some custom coding then you will need to be familiar with the RealMe message request requirements that differ in some way from the OASIS Standard or have additional NZ specific constraints. You should also look at the SAML metadata requirements for RealMe integration.
After successfully connecting to the Message Testing Service, the core steps for technical integration describes what is involved in configuring and connecting your online service to the RealMe ITE and Production environments.