How to decrypt an LTPA cookie and view the user information

Lightweight Third-Party Authentication (LTPA), is an authentication technology used in IBM WebSphere and Lotus Domino products. When accessing web servers that use the LTPA technology it is possible for a web user to re-use their login across physical servers.

In a business that extensively use different IBM products, it is possible to configure LTPA tokens to communicate authentication information between different platforms. For example, an IBM WebSphere Application Server based web application can be configured to propagate the credentials of the logged in user to a WebSphere Process Server based process using LTPA cookies. In a perfect world when everything works fine, there is no issue, but there are several instances when communication does not work as expected and there is a need to see the values that was sent and received as LTPA cookies for diagnostic purposes.

Read more »

Read More

java.io.IOException: FATAL ERRORS encountered by WSDL2Java tool

We will discuss how to resolve the below error message in Rational Application Developer (RAD) when you start the WebSphere Application Server


Error messages were issued.
java.io.IOException: FATAL ERRORS encountered by WSDL2Java tool.
at com.ibm.ws.webservices.wsdl.Parser.generate(Unknown Source)
at com.ibm.ws.webservices.wsdl.Parser.generate(Unknown Source)
at com.ibm.ws.webservices.tools.wsad.WSDL2Java._execute(Unknown Source)
at com.ibm.ws.webservices.tools.wsad.WSDL2JavaBase.execute(Unknown Source)
at com.ibm.etools.webservice.command.adapter.CommandToCommand.execute(Unknown Source)
at com.ibm.ast.ws.v7.jaxrpc.jee5.stub.WSDeployStub.execute(Unknown Source)
at sun.reflect.GeneratedMethodAccessor96.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)


In WebSphere Application Server, when you deploy or publish an application, it uses the WSDL files and generates the serializer and deserializer, even if it was already generated as a part of the proxies. This error message indicates that the WSDL file was either corrupted or not contains XSDs that does not match up. 


If you have your WSDLs changed recently, there could be chances that the server cache still has old WSDLs. We will discuss how to get rid of this error. Please follow the below steps

Read more »

Read More

SECJ0371W: Validation of the LTPA token failed because the token expired with the following info: {0}

If you are seeing this exception in the logs of Websphere 7 server, it is mainly because the LTPA token has expired and therefore, it cannot be validated.


Based on different scenarios, the reason of this error may be different

Read more »

Read More

Websphere 7.0 Cannot load XSL files from com.ibm.ws.runtime.jar

WebSphere 7.0 Cannot load XSL files from com.ibm.ws.runtime.jar


If you are seeing the below error when WebSphere server is started

Cannot load XSL files from <install_root>/plugins/com.ibm.ws.runtime.jar

This error is displayed because during server startup some WAS Product APIs are called to retrieve product version information. The xsl files are required in order for those APIs to work properly.

This issue is fixed in fixpack 7.0.0.1

To install fix pack follow the below steps

Read more »

Read More

NullPointerException in GenericTypeResolver on IBM JDK6

This problem is due to a slightly different implementation of "java.beans.PropertyDescriptor" class in the IBM JDK. This issue has been fixed in Spring 2.5.5 or higher

You can download the latest versions of Spring from http://www.springsource.org/download

Read More