RequestedAuthnContext Comparison="exact"

Doan, Tommy tdoan at
Thu Sep 26 18:43:58 EDT 2019

I'm experimenting with p:disallowedFeatures-ref="SAML2.SSO.FEATURE_AUTHNCONTEXT" in relying party. I happened to notice that one particular SP, Handshake, sends what appears to be an unusual RequestedAuthnContext in the AuthnRequest.

<samlp:AuthnRequest AssertionConsumerServiceURL=""
    <samlp:NameIDPolicy AllowCreate="true"
    <samlp:RequestedAuthnContext Comparison="exact">

That Comparison="exact" parameter is disallowed and logged by the IdP as expected, but the SP then throws an error. So there doesn't appear to be a way to interact with this SP with disallowedFeatures-ref in place.

The reason I'm working with disallowedFeatures-ref is to determine how best to require MFA for lots of SPs, and eventually all of them, through relying party configuration. It seems like a good idea to use disallowedFeatures-ref in that strategy, and I'm not sure what to do about an SP like Handshake. I understand an SP asking for a specific authn context, but that's not really even being done here. Maybe it's unintentional or a configuration error. Is the only option to take this up with the SP admins, or is there another approach on the IdP side to prevent an authn context request from interfering with the relying party configuration to require MFA?

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the users mailing list