Versions Compared

Old Version 4

changes.mady.by.user Scott Cantor

Saved on

compared with

New Version Current

changes.mady.by.user Scott Cantor

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Options common to SAML profiles:

includeConditionsNotBeforeBooleantrueWhether to include a NotBefore attribute in assertionsassertionLifetimeDurationPT5MLifetime of assertionssignAssertionsBooleanfalseWhether to sign assertions

Name

Type

Default

Description

additionalAudiencesForAssertionCollection<String>Additional values to populate into audience restriction condition of assertions

signResponses

Boolean

varies by profile

Whether to sign responses

signRequests

Boolean

false

Whether to sign requests

Guidance

It isn't too common to need any of these options, and they should be changed only with care.

The additionalAuduencesForAssertion and includeConditionsNotBefore settings provide ways to work around bugs in other systems. You should never use these settings without obtaining a commitment from the other system's owner to fix their bugs.

The assertionLifetime setting does not involve control over the session with the relying party, it's only relevant in delegation scenarios.

The signResponses default varies by profile, see the notes on the individual profile pages.If you need to enable the signAssertions option, and you control the SP's metadata, you should generally add the WantAssertionsSigned flag to it in place of using this option. Related, the idp.saml.honorWantAssertionsSigned property can be turned off to globally ignore that flag in metadata should you wish to do so.