An error occurred while generating access token from refresh token in RSA Governance & Lifecycle
Originally Published: 2016-06-13
Article Number
Applies To
RSA Version/Condition: 7.x and above
Issue
01/09/2019 12:26:24.170 ERROR (pool-5735-thread-1) [com.aveksa.server.core.oauth2.OAuth2ServiceProvider] Error occured com.aveksa.server.core.oauth2.OAuth2Exception: Error occured while generating access token from refresh token : Error occured while generating access token from refresh token : Not Found
at com.aveksa.server.core.oauth2.OAuth2Handler.getTokenFromRefreshToken(OAuth2Handler.java:195)
at com.aveksa.server.core.oauth2.OAuth2ServiceProvider.getAccessTokenUsingRefreshToken(OAuth2ServiceProvider.java:156)
at com.aveksa.gui.util.oauth2.TokenExpiryHandler.run(TokenExpiryHandler.java:50)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
01/09/2019 12:26:24.174 ERROR (pool-5735-thread-1) [com.aveksa.gui.util.oauth2.TokenExpiryHandler] Error occured while generating access token from refresh token java.lang.Exception: com.aveksa.server.core.oauth2.OAuth2Exception: Error occured while generating access token from refresh token : Error occured while generating access token from refresh token : Not Found at com.aveksa.server.core.oauth2.OAuth2ServiceProvider.getAccessTokenUsingRefreshToken(OAuth2ServiceProvider.java:163)
at com.aveksa.gui.util.oauth2.TokenExpiryHandler.run(TokenExpiryHandler.java:50)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
Caused by: com.aveksa.server.core.oauth2.OAuth2Exception: Error occured while generating access token from refresh token : Error occured while generating access token from refresh token : Not Found
at com.aveksa.server.core.oauth2.OAuth2Handler.getTokenFromRefreshToken(OAuth2Handler.java:195)
at com.aveksa.server.core.oauth2.OAuth2ServiceProvider.getAccessTokenUsingRefreshToken(OAuth2ServiceProvider.java:156)
... 4 more
at com.aveksa.server.core.oauth2.OAuth2Handler.getTokenFromRefreshToken(OAuth2Handler.java:195)
at com.aveksa.server.core.oauth2.OAuth2ServiceProvider.getAccessTokenUsingRefreshToken(OAuth2ServiceProvider.java:156)
at com.aveksa.gui.util.oauth2.TokenExpiryHandler.run(TokenExpiryHandler.java:50)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
01/09/2019 12:26:24.174 ERROR (pool-5735-thread-1) [com.aveksa.gui.util.oauth2.TokenExpiryHandler] Error occured while generating access token from refresh token java.lang.Exception: com.aveksa.server.core.oauth2.OAuth2Exception: Error occured while generating access token from refresh token : Error occured while generating access token from refresh token : Not Found at com.aveksa.server.core.oauth2.OAuth2ServiceProvider.getAccessTokenUsingRefreshToken(OAuth2ServiceProvider.java:163)
at com.aveksa.gui.util.oauth2.TokenExpiryHandler.run(TokenExpiryHandler.java:50)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
Caused by: com.aveksa.server.core.oauth2.OAuth2Exception: Error occured while generating access token from refresh token : Error occured while generating access token from refresh token : Not Found
at com.aveksa.server.core.oauth2.OAuth2Handler.getTokenFromRefreshToken(OAuth2Handler.java:195)
at com.aveksa.server.core.oauth2.OAuth2ServiceProvider.getAccessTokenUsingRefreshToken(OAuth2ServiceProvider.java:156)
... 4 more
Cause
AFX connectors with RESTful Web Service template can take advantage of OAuth authorization protocol. OAuth allows "client applications" to get limited access to the "endpoints/servers" using authorization token rather than authentication using credentials. Authorization tokens have limited lifetime and will expire. Clients need to retrieve a new token before authorization token expires using refresh token mechanism. AFX does this automatically in the background but can fail if connection details are not valid and up-to-date. Every time AFX fails to retrieve a new access token, it logs an error in the aveksaServer.log.
Resolution
- Make sure you can retrieve the OAuth 2.0 access token manually. To do so, click AFX > Connectors > [Connector Name] > Edit > Settings.
- Click Proceed for authorization and acquire an access token. A new authentication window will open. If you cannot complete this step, make sure all the connection details are valid and up-to-date. You may need to reach out to your AFX endpoint administrator to validate the connection details.
Notes
Related Articles
Generic REST Collector fails with 'Access token has expired' error in RSA Identity Governance & Lifecycle 292Number of Views Token seed import fails with 'Import Token failure' error for RSA Authentication Manager 609Number of Views When replacing an RSA SecurID software token with a new software token the token PIN is not carried over to the new token 593Number of Views RSA SecurID software token is distributed in a disabled state when requested with modified software token profiles via the… 517Number of Views How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device 705Number of Views
Trending Articles
Quick Setup Guide - Passwordless Authentication in Windows MFA Agent for Active Directory RSA Authentication Manager 8.9 Release Notes (January 2026) Artifacts to gather in RSA Identity Governance & Lifecycle RSA Governance & Lifecycle 8.0.0 Administrators Guide RSA Governance & Lifecycle 8.0.0 Installation Guide
Don't see what you're looking for?