Previous Topic: SmDmsUser.getGroups() and SmDmsUser.getRoles() Function Calls (135395)Next Topic: Session Index Updates Causes SLO to Fail (123496)


SAML 2.0 Assertion Does Not Have the Correct Timestamp (128759)

Symptom:

The SAML assertion generated by SiteMinder does not contain the expected timestamp because of the SessionNotOnOrAfter attribute that SiteMinder automatically adds to the assertion. You cannot omit this parameter.

Solution:

To make the configuration of the SessionNotOnOrAfter assertion parameter more flexible, two new properties have been added to the C and Perl CLIs.

The two properties are:

For more information about these properties, see the Programming Guide for C or the Programming Guide for Perl.

STAR Issue: 19635319