December Release - Impact for your Users

When updating to the latest SCA v1.71 (iOS) / v1.30 (Droid) any existing session token becomes invalid.

Therefore, the next time the SCA is started, the user ends up on the login screen, where they have to log in again as normal.

Enduser Impact iOS with Conditional Access

When updating to the latest SCA v1.71. Any existing session token becomes invalid. The new app on your devices uses for your Conditional Access the new Enterprise-App-ID.

Therefore, the next time the SCA is started, the user ends up on the login screen, where they have to log in again as normal.

Manual to update your CA-Policy accordingly: https://docs.secure-contacts.com/introduction/december-release-enterprise-id-change/updating-your-conditional-access-policy-with-the-new-enterprise-id

Known Issue:

Once Conditional Access is configured for the SCA for iOS, it can happens in rare cases that the login is temporarily not possible due to Microsoft Authenticator cache holds authentication-token. This error is handled by the app and SCA displays the error-ID from Azure AAD with a short description of the error.

Users need to close the SCA-App and have to wait for 2 hours, the authentication cache to expire.

In Case a user receives this error message:

The following steps need to be done, in order to be able to login: 1) Tap on OK to close the app.

2) Wait for 2h (Caller-Identification does still work)

3) Open the app again after 2h.

4) Login again.

Last updated 5 months ago