000035416 - Error "Key negotiation exchange failed. Server response was CRED_MISMATCH" with RSA Authentication Agent SDK 8.6 for Java

Document created by RSA Customer Support Employee on Sep 4, 2017Last modified by RSA Customer Support on Jun 5, 2019
Version 2Show Document
  • View in full screen mode

Article Content

Article Number000035416
Applies ToRSA Product Set: SecurID
RSA Product/Service Type:  RSA Authentication Agent SDK 8.6 for Java
RSA Version/Condition: 8.6
Platform: Java
 
IssueThe error message below is reported by the agent application:
 
[2017-08-07 07:53:02,203] ERROR main - Error in processing Authn request: connect exception processing key negotiation request: com.rsa.authmgr.commonagent.k: Key negotiation exchange failed. Server r esponse was CRED_MISMATCH
[2017-08-07 07:53:02,203] ERROR main - Error in initial AuthnReq/Rsp for serverTime.Error in processing Authn request: connect exception processing key negotiation request: com.rsa.authmgr.commonagent .k: Key negotiation exchange failed. Server response was CRED_MISMATCH Can't create api: com.rsa.authagent.authapi.AuthAgentException: Error in initial AuthnReq/Rsp for serverTime.Error in processing Authn request: connect exception processing key negotiation request: co m.rsa.authmgr.commonagent.k: Key negotiation exchange failed. Server response was CRED_MISMATCH

com.rsa.authagent.authapi.AuthAgentException: com.rsa.authagent.authapi.AuthAgentException: Error in initial AuthnReq/Rsp for serverTime.Error in processing Authn request: connect exception processing key negotiation request: com.rsa.authmgr.commonagent.k: Key negotiation exchange failed. Server response was CRED_MISMATCH


at com.rsa.authagent.authapi.AuthSessionFactory.a(AuthSessionFactory.java)
at com.rsa.authagent.authapi.AuthSessionFactory.getInstance(AuthSessionFactory.java)
at sample.AuthUser.<init>(AuthUser.java:32)
at sample.AuthUser.main(AuthUser.java:62)



 
CauseThis CRED_MISMATCH (Credential Mismatch) is due to node secret mismatch.
ResolutionDelete the node secret from Authentication Manager and/or the SDK-based agent as needed.

Attachments

    Outcomes