Sample WS-Federation web app
By following this guide, you will be able to deploy a WS-Federation-based web application and enable login for it using the Passive Security Token Service (Passive STS) of Indryve Endorse.
Info
Indryve Endorse uses its passive security token service (Passive STS) as its WS-Federation implementation. Passive STS is capable of issuing SAML 1.1 and 2.0 security tokens. To request a SAML 2.0 security token, the Request Security Token (RST) should be sent to the passive STS endpoint with the token type,
SAMLV2.0
. If no RST is specified, Indryve Endorse issued a SAML 1.1 token by default.
Prerequisites
- Download Apache Tomcat 8.x and install it. Tomcat server installation location will later be referred to as
<TOMCAT_HOME>
in this guide. - It is recommended that you use a hostname that is not
localhost
to avoid browser errors. Modify your machine’s/etc/hosts
entry to reflect this.
Info
Note that
ind2is.local
is used in this documentation as an example, but you must modify this when configuring the authenticators or connectors with this sample application.
Download the Passive STS Sample application from the latest release assets.
Deploy the sample app
To deploy the sample web app on a web container:
- Copy the application’s downloaded
.war
file into thewebapps
directory of the Tomcat folder. - Start the Tomcat server.
Configure sample properties
To configure additional properties for the sample application:
- Add the following configurations to the
web.xml
file in<TOMCAT_HOME>/apache-tomcat-<version>/webapps/PassiveSTSSampleApp/WEB-INF
. - Specify
idpUrl
as the Identity Server’s Passive STS URL.
<init-param>
<param-name>idpUrl</param-name>
<param-value>https://localhost:9443/passivests</param-value>
</init-param>
- Specify the
replyURL
as the URL of the web app.
<init-param>
<param-name>replyUrl</param-name>
<param-value>http://localhost:8080/PassiveSTSSampleApp/index.jsp</param-value>
</init-param>
- Specify the
realm
as a unique identifier for the web app.
<init-param>
<param-name>realm</param-name>
<param-value>PassiveSTSSampleApp</param-value>
</init-param>
- Restart the tomcat server.
Configure the service provider
- On the Indryve Endorse Console, go to Applications.
- Click New Application and select Standard-Based Application.
- Enter the following details:

Name | Give a unique name to identify your application.e.g.:PassiveSTSSampleApp |
Protocol | Select WS-Federation. |
Realm | This should be a unique identifier for the web app. Provide the same realm name given to the web app you are configuring WS-Federation for.e.g.:PassiveSTSSampleApp |
Reply URL | Provide the URL of the web app you are configuring WS-Federation for. This endpoint URL will handle the token response.http://localhost:8080/PassiveSTSSampleApp/index.jsp |
- Click Register to complete the registration.
- Go to the User Attributes tab and click Add User Attribute, and add the following attributes:
http://wso2.org/claims/username
http://wso2.org/claims/emailaddress
- Select
http://wso2.org/claims/emailaddress
as the Subject attribute. - Click Update to save your configurations.
Tip
Currently, the signing algorithm used for WS-Federation by default is
rsa-sha256
, and the digest algorithm used issha256
. To change the default algorithms, add the following configuration in thedeployment.toml
file found in the<IS_HOME>/repository/conf
directory. The example given below sets the signing algorithm torsa-sha1
and the digest algorithm tosha1
.[sts] signature_algorithm = "http://www.w3.org/2001/04/xmldsig-more#rsa-sha1" digest_algorithm = "http://www.w3.org/2001/04/xmlenc#sha1"
Try it out
Info
When redirecting your users to Indryve Endorse Passive STS endpoint, the following (optional) parameters are sent in the request from the sample application.
- wa=wsignin1.0: specifies whether Indryve Endorse should issue a token for the relying party (this is the default action).
- wa=wsignout1.0: specifies whether Indryve Endorse should log the user out.
- wreply={replyUrl}: specifies where the response should be sent.
Using a Network tracer such as a SAML tracer is recommended to analyze the HTTP request and responses in this scenario. With a tracer, you will be able to view the parameters mentioned above and also see the SAML token that is issued from Indryve Endorse.
- Access one of the following links on your browser and click Login.
- To get a SAML 1.1 token: http://localhost:8080/PassiveSTSSampleApp/index.jsp
- To get a SAML 2.0 token: http://localhost:8080/PassiveSTSSampleApp?samlv=2-0
- Login using your credentials.
- Provide the required consent. You will be redirected to the Indryve Endorse WS-Federation Service and then redirected back to the configured
replyUrl
.
You will see the WS-Federation response with the requested claims on the screen.