The profiles specification for Security Assertion Markup Language 2.0 (SAML 2.0) defines single sign-on based on a web browser. This topic provides instructions on how to use the sample available in the WSO2 Identity Server to demonstrate how to configure SSO using SAML 2.0 with a sample service provider.
|title||Click here to view vital information when running this sample in WSO2 Application Server|
|title||When running this sample on AS|
Both this SSOAgentSample application and WSO2 Application Server contain different versions of the same slf4j jar. As a solution you can select ONE of the following approaches.
- Remove log4j-over-slf4j-1.6.1.jar file from travelocity.com.war/WEB-INF/lib directory and deploy.
<AS_HOME>/repository/conf/tomcat/webapp-classloading-environments.xml to resolve the
slf4j conflict and restart the WSO2 Application Server. This change is done so as not to expose the
org.slf4j.* package from WSO2 Carbon.
Tip: If you wish to change properties like the issuer ID, consumer URL and IdP URL, you can edit the
travelocity.properties file found inside the
travelocity.com/WEB-INF/classes directory. This sample uses the following default values.
|A unique identifier for this SAML 2.0 Service Provider application|
|The URL of the SAML 2.0 Assertion Consumer|
|The URL of the SAML 2.0 Identity Provider|
If you edit the travelocity.properties file, you must restart the Apache Tomcat server for the changes to take effect.