000034609 - Timer already cancelled error appears when attempting TeleSign OOB SMS in RSA Adaptive Authenthentication (on Premise) 7.1 P2

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

Article Content

Article Number000034609
Applies ToRSA Product Set: Adaptive Authentication (OnPrem)
RSA Version/Condition: 7.1 P2
 
IssueCustomer reported they see the following error in aa_server.log (rsa/logs/aa_server.log) when attempting an OOB SMS challenge with Telesign Plugin
 
ERROR [http-bio-8247-exec-223] [com.rsa.csd.ws.impl.AdaptiveAuthenticationImpl] com.rsa.csd.mcf.McfException: 
Timer already cancelled.
com.rsa.csd.mcf.McfException: Timer already cancelled.
at com.rsa.csd.impl.UserCredentialManagerImpl.challenge(UserCredentialManagerImpl.java:394)
at com.rsa.csd.ws.impl.helper.GenericHelper.doChallenge(GenericHelper.java:1053)
at com.rsa.csd.ws.impl.helper.GenericHelper.doChallenge(GenericHelper.java:1129)
at com.rsa.csd.ws.impl.helper.ChallengeHelper.challengeUser(ChallengeHelper.java:229)
at com.rsa.csd.ws.impl.AdaptiveAuthenticationImpl.challenge(AdaptiveAuthenticationImpl.java:472)
at axis.delegate.aa_7_0.AdaptiveAuthenticationDelegate.challenge
(AdaptiveAuthenticationDelegate.java:131)
at com.rsa.csd.ws.axis.generated.AdaptiveAuthenticationSkeleton.challenge
(AdaptiveAuthenticationSkeleton.java:64)
at com.rsa.csd.ws.axis.generated.AdaptiveAuthenticationMessageReceiverInOut.invokeBusinessLogic
(AdaptiveAuthenticationMessageReceiverInOut.java:48)
at org.apache.axis2.receivers.AbstractInOutMessageReceiver.invokeBusinessLogic
(AbstractInOutMessageReceiver.java:40)
at org.apache.axis2.receivers.AbstractMessageReceiver.receive
(AbstractMessageReceiver.java:114)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:173)
at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest
(HTTPTransportUtils.java:173)


 
CauseEngineering investigated and found to be a bug
ResolutionA workaround was provided to resolve the issue. Steps below

Please replace the pmcore-xx.jar attached to JIRA AA-18312 in AdaptiveAuthentication\WEB-INF\lib taking the backup of old one.
Restart the servers

Attachments

    Outcomes