Implementing the Portal Single Sign-Out

Implementing the Portal Single Sign-On is the common, however implementing the Portal Single Sign-Out is not common. This article explains how we implement the Portal Single Sign-Out.

The first thing to do is to extend the “com.ibm.wps.engine.commands.LogoutUserAuth” class. Let’s pick a name “com.mycomp.auth.LogoutUserAuth”. Override this function “protected void doPreLogout(RunData arg0) throws WpsException”. Make sure that you put logic within this function to do the Applications Logout. This Logic can be just a simple API call, or HTTP Logout request call.

Create the JAR file for this file, let’s pick a name: “auth-1.0.jar”

The following steps must be taken to implement to the Portal:

1. Copy the auth-1.0.jar into the <Portal_Root>/shared/app folder
2. Configure the Resource Environment Providers (in both nodes):
3. Login to WAS ND Console
4. Navigate to Resources – Resource Environment Providers
5. Select the node (or multiple nodes if you have multiple nodes in your cluster)
6. Configure the WP ConfigService, open the Custom Properties. Make sure that the command.login value is LoginUserAuth, and the command.logout value is LogoutUserAuth.
7. Configure the WP LoaderService, open the Custom Properties. Make sure that command.path value is com.mycomp.auth;com.ibm.wps.engine.commands,com.ibm.wps.dynamicui.commands
8. Restart the Portal