|Issuer||Specify the Issuer. This is the ||travelocity.com|
Service Provider Qualifier
This value is needed only if you have to configure multiple SAML SSO inbound authentication configurations for the same “Issuer” Issuer value. When an “Service a Service Provider Qualifier” Qualifier is defined here, it will be appended to the end of the “Issuer” Issuer value when registering the SAML SP in the Identity Server.
Ex : If For example, if you specify travelocity.com as the “Issuer” Issuer and sp1 as the “Service Service Provider Qualifier”Qualifier, the configuration will be registered in IS by the value - as
You can configure any amount a number of SAML SPs with the same “Issuer” Issuer and different “Service Service Provider Qualifier”Qualifiers.
When an “Service a Service Provider Qualifier” Qualifier is defined, the issuer of the SAML SSO authentication request’s issuer request is the value specified as “Issuer” the Issuer in the configuration (ex : travelocity.com). The service provider qualifier value should be sent as a query parameter “spQualifier” , spQualifier with the HTTP request in the following format.
In Travelocity sample SP, this query parameter can be set by modifying
|Assertion Consumer URLs||Specify the Assertion Consumer URLs. This is the URL to which the browser should be redirected to after the authentication is successful. This is the Assertion Consumer Service (ACS) URL of the service provider. The identity provider redirects the SAML2 response to this ACS URL. However, if the SAML2 request is signed and SAML2 request contains the ACS URL, the Identity Server will honor the ACS URL of the SAML2 request. It should have this format: https://(host-name):(port)/acs. You can add multiple assertion consumer URLs for the service provider by entering the URL and clicking the Add button.||http://wso2is.local:8080/travelocity.com/home.jsp|
|Default Assertion Consumer URL|
Since there can be multiple assertion consumer URLs, you must define a Default Assertion Consumer URL in case you are unable to retrieve it from the authentication request.
Specify the NameID format. This defines the name identifier formats supported by the identity provider. The service provider and identity provider usually communicate with each other regarding a specific subject. That subject should be identified through a Name-Identifier (NameID) , which should be in some format so that It is easy for the other party to identify it based on the format. Name identifiers are used to provide information regarding a user.
Select the Certificate Alias from the dropdown. This is used to validate the signature of SAML2 requests and is used to generate encryption. Basically the service provider’s certificate must be selected here. Note that this can also be the Identity Server tenant's public certificate in a scenario where you are doing a tenant specific configuration.
|Response Signing Algorithm|
Specifies the ‘SignatureMethod’ algorithm to be used in the ‘Signature’ element in POST binding. The default value can be configured in the
|Response Digest Algorithm|
Specifies the ‘DigestMethod’ algorithm to be used in the ‘Signature’ element in POST binding. The default value can be configured in the
|Assertion Encryption Algorithm||The algorithm that the SAML2 assertion is encrypted. The default value can be configured in the ||www.w3.org/2001/04/xmlenc#aes256-cbc|
|Key Encryption Algorithm||The algorithm that the SAML2 key is encrypted. The default value can be configured in the ||www.w3.org/2001/04/xmlenc#rsa-oaep-mgf1p|
|Enable Response Signing||Select Enable Response Signing to sign the SAML2 Responses returned after the authentication process.||Selected|
|Enable Signature Validation in Authentication Requests and Logout Requests||Select Enable Signature Validation in Authentication Requests and Logout Requests if you need this functionality configured. This specifies whether the identity provider must validate the signature of the SAML2 authentication request and the SAML2 logout request that are sent by the service provider.||Unselected|
|Enable Assertion Encryption||Enable Assertion Encryption, if you wish to encrypt the assertion.||Unselected|
|Enable Single Logout|
Select Enable Single Logout so that all sessions are terminated once the user signs out from one server. If single logout is enabled, the identity provider sends logout requests to all service providers. Basically, the identity provider acts according to the single logout profile. If the service provider supports a different URL for logout, you can enter a SLO Response URL and SLO Request URL for logging out. These URLs indicate where the request and response should go to. If you do not specify this URL, the identity provider uses the Assertion Consumer Service (ACS) URL.
WSO2 Identity Server supports both SAML Back-Channel Logout and SAML Front-Channel Logout methods. By default, when you select Enable Single Logout the Back-Channel Logout is enabled. In order to enable SAML Front-Channel Logout, you can either select Front-Channel Logout (HTTP Redirect Binding) or Front-Channel Logout (HTTP POST Binding).
|Enable Attribute Profile||Select Enable Attribute Profile to enable this and add a claim by entering the claim link and clicking the Add Claim button. The Identity Server provides support for a basic attribute profile where the identity provider can include the user’s attributes in the SAML Assertions as part of the attribute statement. Once you select the checkbox to Include Attributes in the Response Always, the identity provider always includes the attribute values related to the selected claims in the SAML attribute statement.||Unselected|
|Enable Audience Restriction||Select Enable Audience Restriction to restrict the audience. You may add audience members using the Audience text box and clicking the Add button.||Unselected|
|Enable Recipient Validation||Select this if you require validation from the recipient of the response.||Unselected|
|Enable IdP Initiated SSO||Select the Enable IdP Initiated SSO checkbox to enable this functionality. When this is enabled, the service provider is not required to send the SAML2 request.||Unselected|
|Enable IdP Initiated SLO||Select the Enable IdP Initiated SLO checkbox to enable this functionality. You must specify the URL.||Unselected|
|Enable Assertion Query Request Profile||Select the Enable Assertion Query Request Profile checkbox to query assertions that are persisted to the database when you login to the service provider application. For more information, see Querying SAML Assertions.||Unselected|
|IdP Entity ID Alias|
This value can override the “Identity Provider Entity ID” specified under SAML SSO Inbound Authentication configuration in “Resident IdP”. The “Identity Provider Entity ID” is used as the “issuer” of the SAML responses generated from IS. By default, all the SAML responses issued by IS will have the issuer value similar to “Identity Provider Entity ID” in Resident IdP’s SAML SSO inbound authentication configuration. But if you want that value to be unique for your SAML SP configuration, you can specify that value here, so that the IdP Entity ID will be overridden with this IdP Entity ID Alias value.
In Travelocity sample SP, this value can be set by modifying SAML2.IdPEntityId value mentioned inside the travelocity.com/WEB-INF/classes/travelocity.properties file to the IdP Entity ID Alias you define in the SAML SP configuration.
|any valid URL/URI|