000034660 - Adaptive Authentication (On Premise) 7.0 customer seeing 'The remote server returned an error: (400) Bad Request.'

Document created by RSA Customer Support Employee on Jan 23, 2017Last modified by RSA Customer Support Employee on Apr 21, 2017
Version 2Show Document
  • View in full screen mode

Article Content

Article Number000034660
Applies ToRSA Product Set: Adaptive Authentication (OnPrem)
RSA Product/Service Type: Adaptive Authentication (OnPrem)
RSA Version/Condition: 7.0
 
IssueAn Adaptive Authentication (On Premise) customer noticed an error in the log file of their monitoring software:
'The remote server returned an error: (400) Bad Request.'
 
TasksA search of AA log files revealed the following errors around the same time as the 
bad request error:
aa_server.log:
2017-01-02 23:15:43,993 ERROR [http-8080-168] [] [] [com.rsa.csd.ws.util.BasicWSClientAuthenticator] - <Error in authenticating user:::null>
2017-01-02 23:15:43,993 ERROR [http-8080-168] [] [] [com.rsa.csd.ws.impl.AdaptiveAuthenticationImpl] - <com.rsa.csd.ws.impl.AdaptiveAuthProcessException: Reason Code: 1604
Description: Authentication Error 
Caller Authentication failed>
com.rsa.csd.ws.impl.AdaptiveAuthProcessException: Reason Code: 1604
Description: Authentication Error 
Caller Authentication failed
aa_server.soapcalls.log:
<ns1:reasonDescription>Unable to complete requests due to processing error:
----------------------------------------------------------
Reason Code: 1604
Description: Authentication Error 
Caller Authentication failed
</ns1:reasonDescription>
ResolutionThe Caller Authentication Error was found in a Soap response. 
Tracking back to the corresponding Soap request found a callerId that did not exist in the wscredentialmanager webpage.
Customer could resolve the issue by one of the following:
1. Add the callerId to the wscredentialmanager
2. Change the Soap request to use an existing callerId & callerCredential
 

Attachments

    Outcomes