Importing new token seed record fails with browser error - AM
Originally Published: 2014-06-05
Article Number
Applies To
RSA Authentication Manager (AM) 8.X
Microsoft Internet Explorer
Mozilla Firefox
Google Chrome
Safari
Issue
When creating new token import job, after browsing to the xml seed file and clicking submit, the browser displays error: "The connection was reset. The connection to the server was reset while the page was loading. The site could be temporarily unavailable or too busy. Try again in a few minutes. If you are unable to load any pages, check your computer's network connection. If your computer or network is protected by a firewall or proxy, make sure the <browser> is permitted to access the Web."
Resolution
1) Use different browsers, try IE, Chrome, Firefox, Safari, etc...
2) Clear the cookies and cache from the browser.
3) Create a new super admin in the internal database with a simple password and use it to import...(remove it afterwards)
4) Try a different PC.
5) Verify firewall and/or proxy settings aren't preventing access and add appropriate exclusion.
Along with these, make sure to patch to the latest stable build of RSA Authentication Manager and this should resolve your ability to import those tokens.
Related Articles
Authentication test login fails with "ERROR: Authentication Module: XXXXXX not found in configuration" in RSA Identity Gov… Number of Views New Delivery Method for Token Seed Records Number of Views Distribute One Software Token Using Dynamic Seed Provisioning Number of Views Token seed import fails with 'Import Token failure' error for RSA Authentication Manager Number of Views RSA RSA SecurID - Force all tokens to be in New PIN mode without clearing PIN Number of Views
Trending Articles
Authentication Manager Supported Hardware and Upgrade Paths RSA Authentication Manager Upgrade Process Artifacts to gather in RSA Identity Governance & Lifecycle How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device Authentication Manager 'Principal Does Not Possess Authenticator' Error for Users with Multiple IDs
Don't see what you're looking for?
