2.1.0
Version 2.1.0 has been released to adjust for changes required as a result of the RealMe re-platforming from Datacom to Azure, and to support Silverstripe CMS 3.
Warning: You must not use version 2.1.0 in a production environment until Sunday 11 April 2021 (to coincide with the changes being made by DIA).
You may safely upgrade to this version on any pre-production environments now. There is only one change from version 2.1.0-rc2 which is passing the BackURL through via RelayState, this is to avoid issues with Chrome and other browsers that adhere to the new samesite cookie attribute causing session cookies to get reset when you return from RealMe.
Once you have upgraded to this version, you must also update the Identity Provider certificate for your chosen environment (either MTS, ITE or Production). The correct certificate can be found in the appropriate re-platforming bundle on the RealMe Developers website.
- For production environments, the certificate filename has changed for both logon and assert (the same certificate is used for both). The new certificate filename for production is
signing.realme.govt.nz.cer
. - For ITE environments, if you are using the assertion service then the certificate filename has changed. RealMe now uses the same certificate for logon and assert, so your certificate filename should now be
ite.signing.logon.realme.govt.nz.cer
(even though you are using assert).