CIS2 Authentication release 10.04

As part of our ongoing learning from the passkeys private beta, we're adding further messages to ensure that users understand which authenticator they have registered.

We've also implemented a number of minor fixes and security improvements to CIS2 Authentication.

What this means for you

Health and social care professionals:

• This change impacts health and care professionals registering a new passkey as part of the private beta.
• If you select the option to register a passkey, but your device settings indicate that you've bound a different authenticator (such as Windows Hello), we'll confirm upon successful registration which authenticator you have bound. The authenticator you bind will be available to use when you next log in.

Organisations providing IT support for health and social care professionals:

• Should experience no change. 

Health and social care application suppliers:

• Should experience no change. 

Registration Authorities:

• This change impacts health and care professionals registering a new passkey as part of the private beta.
• If you select the option to register a passkey for your staff member, but their device indicates that they have bound a different authenticator (such as Windows Hello), we'll confirm upon successful registration what authenticator was bound. The bound authenticator will also be confirmed under their profile page. 

Why we are doing this

We are making a number of minor security changes and fixes as part of our normal maintenance pattern.