You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: en/asgardeo/docs/get-started/try-samples/ws-federation-webapp.md
+11-9Lines changed: 11 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,9 +5,8 @@ By following this guide, you will be able to deploy a WS-Federation-based web ap
5
5
!!! info
6
6
{{product_name}} uses its passive security token service (Passive STS) as its WS-Federation implementation.
7
7
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, {{product_name}} issued a SAML 1.1 token by default.
8
-
---
9
8
10
-
###Prerequisites
9
+
## Prerequisites
11
10
12
11
- Download [Apache Tomcat 8.x](https://tomcat.apache.org/download-80.cgi){:target="_blank"} and install it. Tomcat server installation location will later be referred to as `<TOMCAT_HOME>` in this guide.
13
12
@@ -28,7 +27,8 @@ To deploy the sample web app on a web container:
28
27
To configure additional properties for the sample application:
29
28
30
29
1. Add the following configurations to the `web.xml` file in `<TOMCAT_HOME>/apache-tomcat-<version>/webapps/PassiveSTSSampleApp/WEB-INF`.
31
-
- Specify `idpUrl` as the Identity Server's Passive STS URL.
30
+
- Specify Asgardeo Passive STS URL as `idpUrl`.
31
+
32
32
```xml
33
33
<init-param>
34
34
<param-name>idpUrl</param-name>
@@ -37,6 +37,7 @@ To configure additional properties for the sample application:
37
37
```
38
38
39
39
- Specify the `replyURL` as the URL of the web app.
40
+
40
41
``` xml
41
42
<init-param>
42
43
<param-name>replyUrl</param-name>
@@ -45,6 +46,7 @@ To configure additional properties for the sample application:
45
46
```
46
47
47
48
- Specify the ` realm ` as a unique identifier for the web app.
49
+
48
50
``` xml
49
51
<init-param>
50
52
<param-name>realm</param-name>
@@ -54,9 +56,9 @@ To configure additional properties for the sample application:
54
56
55
57
2. Restart the tomcat server.
56
58
57
-
## Configure the service provider
59
+
## Configure the application in Asgardeo
58
60
59
-
1. On the WSO2 Identity Server Console, go to **Applications**.
61
+
1. On the {{ product_name }} Console, go to **Applications**.
60
62
61
63
2. Click **New Application** and select **Standard-Based Application**.
62
64
@@ -68,25 +70,25 @@ To configure additional properties for the sample application:
68
70
<tr>
69
71
<td>Name</td>
70
72
<td>
71
-
Give a unique name to identify your application.
73
+
An unique name to identify your application.
72
74
<p>e.g.:<code>PassiveSTSSampleApp</code></p>
73
75
</td>
74
76
</tr>
75
77
<tr>
76
78
<td>Protocol</td>
77
-
<td>Select <b>WS-Federation</b>.</td>
79
+
<td><b>WS-Federation</b>.</td>
78
80
</tr>
79
81
<tr>
80
82
<td>Realm</td>
81
83
<td>
82
-
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.
84
+
An unique identifier for the web app. Provide the same realm name given to the web app you are configuring WS-Federation for.
83
85
<p>e.g.:<code>PassiveSTSSampleApp</code></p>
84
86
</td>
85
87
</tr>
86
88
<tr>
87
89
<td>Reply URL</td>
88
90
<td>
89
-
Provide the URL of the web app you are configuring WS-Federation for. This endpoint URL will handle the token response.
91
+
URL of the web app you are configuring WS-Federation for. This endpoint URL will handle the token response.
0 commit comments