|Applies To||RSA Product Set: ClearTrust|
RSA Product/Service Type: Access Manager
RSA Version/Condition: 6.2
RSA Product/Service Type: Access Manager TAI for WebSphere 8.5
RSA Version/Condition: 5.0 SP1
Symptoms on RSA Access Manager server
Symptoms on WebSphere with Trust Association Interceptors (TAIs)
There can be several reasons for this issue:
Q: Should the jcm-6.1.jar and jcmFIPS-6.1.jar not be in this directory at the same time?
A: Either the jcm-6.1 or jcmFIPS-6.1 jar should be present in the directory, but not both. In the TAI, once we retrieve the username from the cookie/header we create a runtimeAPI to validate the details.
Q: What were the old 6.1.0 .jars and which are the current ones? Which replaced which?
A: With WAS 6.1, we supported only the RSA Access Manager Agent 4.7. There was no FIPS support in them. We introduced FIPS in the RSA Access Manager Agent 4.7 SP1, as noted below:
|Notes||This may be a related error:|
015-02-04 08:06:54 -0500 -  - <Critical> - Error creating Runtime API connection: request to axmqaas.geisinger.edu:5608 failed [CT_REPLY_PARSE_ERROR]
There was a similar issue with WebAgents. Refer - CTAG-4965
Not sure, it could be a compatibility issue.
The install and configuration guide for appserver agents 5.0 and 5.0 SP1 have incorrect installation instructions. It specifies for you to install both the jcm and jcmFIPS jars. This is incorrect. You either install one or the other depending if you want FIPS. This is the INCORRECT text, notice the jcm and jcmFIPS. Only one should be present. From the guide,
Place the following .jar files in the WASBASE/lib/ext directory: