Saml 2.0: Why is NotBefore in the schema for SubjectConfirmationData if it is not allowed? -


we have several service providers using saml 2.0 single sign-on , working fine. our recent addition balking because send notbefore attribute on subjectconfirmationdata element. far can tell, part of xsd schema saml 2.0 (https://docs.oasis-open.org/security/saml/v2.0/saml-schema-assertion-2.0.xsd) marked must not in profiles pdf (https://docs.oasis-open.org/security/saml/v2.0/saml-profiles-2.0-os.pdf).

what missing?

as figured out, web browser sso profile - 1 using provide single sign on users identity provider - dictates should not set notbefore. profile sets further limitations schema defined assertion used generically, totally fine.

the service provider @ hand strictly checks compliance , rejects assertion. fact has been working far means other service provider implementations more lenient.


Comments

Popular posts from this blog

What is happening when Matlab is starting a "parallel pool"? -

angular - DownloadURL return null in below code -

php - Cannot override Laravel Spark authentication with own implementation -