Implement a custom single sign-on token for security attribute propagation
We can create our own single sign-on token implementation. The single sign-on token implementation is set in the login Subject and added to the HTTP response as an HTTP cookie.
The cookie name is the concatenation of the SingleSignonToken.getName API and the SingleSignonToken.getVersion API. There is no delimiter. When you add a single sign-on token to the Subject, it also gets propagated horizontally and downstream in case the Subject is used for other Web requests. You must deserialize your custom single sign-on token when you receive it from a propagation login. Consider writing our own implementation to accomplish one of the following tasks:
- Isolate the attributes within our own implementation.
- Serialize the information using custom serialization. Encrypt the information because it is out to the HTTP response and is available on the Internet. You must deserialize or decrypt the bytes at the target and add that information back into the Subject.
- Affect the overall uniqueness of the Subject using the getUniqueID API.
To implement a custom single sign-on token...
- Write a custom implementation of the SingleSignonToken interface.
Many different methods are available for implementing the SingleSignonToken interface. However, make sure the methods that are required by the SingleSignonToken interface and the token interface are fully implemented.
After you implement this interface, we can place it in the APP_ROOT/classes directory. Alternatively, we can place the class in any private directory. However, make sure that the WAS class loader can locate the class and that it is granted the appropriate permissions. We can add the JAR file or directory that contains this class into the server.policy file so that it has the required permissions for the server code.
Tip: All of the token types defined by the propagation framework have similar interfaces. Basically, the token types are marker interfaces that implement the com.ibm.wsspi.security.token.Token interface. This interface defines most of the methods. If we plan to implement more than one token type, consider creating an abstract class that implements the com.ibm.wsspi.security.token.Token interface. All of the token implementations, including the single sign-on token, might extend the abstract class and then most of the work is complete.
To see an implementation of the single sign-on token, see Example: A com.ibm.wsspi.security.token.SingleSignonToken implementation
- Add and receive the custom single sign-on token during WAS logins.
This task is typically accomplished by adding a custom login module to the various application and system login configurations. However, to deserialize the information, we need to plug in a custom login module, which is discussed in a subsequent step. After the object is instantiated in the login module, we can add it to the Subject during the commit method.
The code sample in Example: A custom single sign-on token login module, shows how to determine if the login is an initial login or a propagation login. The difference is whether the WSTokenHolderCallback callback contains propagation data. If the callback does not contain propagation data, initialize a new custom single sign-on token implementation and set it into the Subject. Also, look for the HTTP cookie from the HTTP request if the HTTP request object is available in the callback. We can get the custom single sign-on token both from a horizontal propagation login and from the HTTP request. However, IBM recommends that you make the token available in both places because then the information arrives at any front-end appserver, even if that server does not support propagation.
We can make the single sign-on token read-only in the commit phase of the login module. If we make the token read-only, additional attributes cannot be added within the applications.
- HTTP cookies have a size limitation. Size restrictions should be included in the documentation for the specific browser.
- The WAS runtime does not handle cookies that it does not generate, so this cookie is not used by the runtime.
- The SingleSignonToken object, when in the Subject, does affect the cache lookup of the Subject if we return something in the getUniqueID method.
- Get the HTTP cookie from the HTTP request object during login or from an application. The sample code that is found in Example: An HTTP cookie retrieval shows how we can retrieve the HTTP cookie from the HTTP request, decode the cookie so that it is back to the original bytes, and create the custom SingleSignonToken object from the bytes.
- Add the custom login module to WAS system login configurations that already contain the com.ibm.ws.security.server.lm.wsMapDefaultInboundLoginModule for receiving serialized versions of the custom propagation token.
Because this login module relies on information in the sharedState state that is added by the com.ibm.ws.security.server.lm.wsMapDefaultInboundLoginModule login module, add this login module after the com.ibm.ws.security.server.lm.wsMapDefaultInboundLoginModule login module.
For information on adding the custom login module into the existing login configurations, see Develop custom login modules for a system login configuration for JAAS.
ResultsAfter completing these steps, we have implemented a custom single sign-on token.
Example: A com.ibm.wsspi.security.token.SingleSignonToken implementation
Example: A custom single sign-on token login module
Example: An HTTP cookie retrieval
Security attribute propagation
Propagating security attributes among appservers
Develop custom login modules for a system login configuration for JAAS
Implementing tokens for security attribute propagation