Symptom
SAML SSO is no longer working and in the indexserver trace file, you see the following:
[157862]{57862}[23/-1] 2017-08-02 12:37:59.595306 d Authentication SAMLAuthenticator.cpp(01019) : Conditions: received assertion fragment
<Conditions NotBefore="2017-08-02T17:37:59.783Z" NotOnOrAfter="2017-08-02T18:37:59.783Z">
<AudienceRestriction>
<Audience>SPIP</Audience>
</AudienceRestriction>
</Conditions>
[157862]{57862}[-1/-1] 2017-08-02 12:37:59.595591 d Authentication Connection.cc(03408) : exception during authentication: ERROR [CODE-4230] Invalid SAML assertion: Assertion is not yet valid(StatusCode: , StatusMessage: )
exception 1: no.71004230 (ptime/session/eapi/jdbc/Connection.cc:3383)
Assertion is not yet valid(StatusCode: , StatusMessage: )
NO exception throw location recorded. Stack generation suppressed.
[157862]{57862}[-1/-1] 2017-08-02 12:37:59.595659 e XSSession XSSessionLifecycle.cpp(00333) : Assertion authentication for user failed with reason: Assertion is not yet valid(StatusCode: , StatusMessage: )
Read more...
Environment
HANA 1.0
HANA 2.0
Product
Keywords
KBA , sac , HAN-DB-SEC , SAP HANA Security & User Management , Problem
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.