...
This profile is configured by adding the <ProfileConfiguration xsi:type="saml:SAML2ECPProfile"/> element to a <RelyingParty> definition.
| Code Block |
|---|
| xml |
|---|
| xml |
|---|
| title | Example SAML2 ECP Profile Configurationxml |
|---|
|
<ProfileConfiguration xsi:type="saml:SAML2ECPProfile" />
|
| Code Block |
|---|
| xml |
|---|
| xml |
|---|
| title | Example SAML2 ECP Profile Configuration Overriding some Defaultsxml |
|---|
|
<ProfileConfiguration xsi:type="saml:SAML2ECPProfile"
signAssertions="always"
includeAttributeStatement="true"/>
|
...
In addition, older versions of the IdP do not have the necessary declarations in the handler.xml file to support the profile endpoint for this feature. To fix this, you will need to add in changes that have occurred between the your version of handler.xml and the newer default version. The XML involved is embedded below.
| Code Block |
|---|
| xml |
|---|
| xml |
|---|
| title | "Example additions to handler.xml"xml |
|---|
|
<ProfileHandler xsi:type="SAML2ECP"
inboundBinding="urn:oasis:names:tc:SAML:2.0:bindings:SOAP"
outboundBindingEnumeration="urn:oasis:names:tc:SAML:2.0:bindings:SOAP">
<RequestPath>/SAML2/SOAP/ECP</RequestPath>
</ProfileHandler> |
...