...
To configure WSO2 App Manager for single logout, select Enable Single Logout in the Step 2 - Policies section of creating a Web app, and specify the logout URL of your app as shown below.
| Info |
|---|
However, when developing third party Web applications, do not include hard-coded absolute URLs, in which case, WSO2 AppM will directly invoke the Web app by-passing the gateway. |
WSO2 App Manager internally converts the Web app URL to a gateway URL. When persisting the logout URL, WSO2 App Manager converts it to a gateway URL by the logout acton is appended to the gateway URL by tallying it against the Web app URL. Therefore, you need to enter the complete logout URL always need to start with the Web app URL as shown in the below convention.(including the Web app URL).
For example, if your Web app URL
...
is http://locahost:8080/MyWebapp
...
, the enter the logout URL as follows: http://locahost:8080/MyWebapp/?action=
...
logout
...
.
Configuring the Web app
The configured logout URL of the Web app should be relative, and should not contain absolute references. A sample logout link configuration on a JSP page, is as As a best practice, Web apps should not contain any hard-coded resource paths when proxying through WSO2 App Manager. Similarly, if the resource path configured for the logout action of your Web application is absolute, WSO2 App Manager by-passes the gateway and invokes the direct URL, and the action sequence for single logout is not triggered.
Therefore, the logout link configuration in a JSP page of the Web app should contain a relative reference as follows.
<li><a href=<% out.println(".?action=logout"); %>>Logout</a></li>