Difference between revisions of "SAMLSpecificationVersion"
Thewikiadmin (talk | contribs) (Created page with "By using the SAMLSpecificationVersion, the integrator has the ability to have more fine-grained control of which SAML Specification to use. Each specification corresponds to c...") |
Thewikiadmin (talk | contribs) |
||
| Line 1: | Line 1: | ||
| − | By using the SAMLSpecificationVersion, the integrator has the ability to have more fine-grained control of which SAML Specification to use. Each specification corresponds to configured profile that will generate the necessary information in the SAML assertions so that downstream service provided will have the information in the format it requires. | + | |
| + | By using the SAMLSpecificationVersion, the integrator has the ability to have more fine-grained control of which SAML Specification to use. Each specification corresponds to configured profile that will generate the necessary information in the SAML assertions so that downstream service provided will have the information in the format it requires. | ||
| + | |||
== Hierarchy == | == Hierarchy == | ||
| − | The SAMLSpecificationVersion value will be processed in the following order: | + | |
| + | The SAMLSpecificationVersion value will be processed in the following order: | ||
| + | |||
#Form Submission | #Form Submission | ||
#Service Configuration | #Service Configuration | ||
#Global Value | #Global Value | ||
| − | | + | |
| + | | ||
| + | |||
| + | == Form Submision == | ||
| + | |||
| + | As part of the POST (or GET) request to the STS, the attribute "SAMLSpecificationVersion" allows the administrator to select a specific SAML profile. | ||
| + | |||
| + | | ||
| + | |||
| + | == Service Configuration == | ||
| + | |||
| + | If the respective [https://sts.radiusworks.com/wiki/index.php?title=SAMLConfiguration#SAMLSpecificationVersion service entry] contains a value for SAMLSpecificationVersion then it will be used. | ||
| + | |||
| + | == == | ||
| + | |||
== Global Value == | == Global Value == | ||
| + | |||
Each STS instance should have have a [https://sts.radiusworks.com/wiki/index.php?title=STSSettings#SAMLSpecificationVersion global SAML profile] configured. If no SAMLSpecificationVersion value is provided either in the form submission to the STS, or specified in the respective service, then the global default value. | Each STS instance should have have a [https://sts.radiusworks.com/wiki/index.php?title=STSSettings#SAMLSpecificationVersion global SAML profile] configured. If no SAMLSpecificationVersion value is provided either in the form submission to the STS, or specified in the respective service, then the global default value. | ||
Revision as of 12:27, 4 October 2020
By using the SAMLSpecificationVersion, the integrator has the ability to have more fine-grained control of which SAML Specification to use. Each specification corresponds to configured profile that will generate the necessary information in the SAML assertions so that downstream service provided will have the information in the format it requires.
Hierarchy
The SAMLSpecificationVersion value will be processed in the following order:
- Form Submission
- Service Configuration
- Global Value
Form Submision
As part of the POST (or GET) request to the STS, the attribute "SAMLSpecificationVersion" allows the administrator to select a specific SAML profile.
Service Configuration
If the respective service entry contains a value for SAMLSpecificationVersion then it will be used.
Global Value
Each STS instance should have have a global SAML profile configured. If no SAMLSpecificationVersion value is provided either in the form submission to the STS, or specified in the respective service, then the global default value.
