- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
01-28-2026 06:40 AM
Hi,
Salesforce will be requiring that AuthnContext elements (e.g. MobileTwoFactorContract, Mfa, Fido, etc) be passed in SAML assertions starting Feb 3, 2026. If assertions do not include a valid AuthnContext element, users will be required to perform "device activation" in order to access their Salesforce accounts. We'd like to avoid this extra authentication step if possible.
Does anyone know how to go about setting this up for the Salesforce SAML app from the CyberArk app catalog? will this be automatically updated by the CyberArk team at some point?
Here is more info regarding this change: https://help.salesforce.com/s/articleView?id=005237070&type=1&utm_source=techcomms&utm_medium=email&utm_campaign=FY26_Core_4081804
Thanks,
Austin
01-28-2026 08:32 AM
If you just want to send an Authentication Context value that will suppress the device activation prompt the easiest way is to select a compatible option like TimeSyncToken from the Authentication Context Class option in the trust tab of the SAML app. Note this value will be present in every SAML response (essentially hardcoded) regardless of the factors you challenged the user to use.
There is a setAuthenContextClass() function that can be used in the custom logic section to dynamically set the value based on some scripted logic. So if you do something like require users in certain roles to have an authentication profile with certain factors you could have logic that returns a context value depending on what role the user is in.
In our case our authentication profiles allow multiple factors that would cover multiple context classes. I entered a support ticket to inquire if there is a means of querying the users last used factors (as shown in the users activity tab) so that could be used as input in the custom logic section to be able to map those factors to corresponding context class values and got a laughable response. Waiting for a meeting with our rep to discuss further.
Also note that your SalesForce admins can define trusted IP ranges, which logons originating from there bypass device activation even without the authentication context value, generally worthwhile for your internal network egress IPs.
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!

