AM Auth SDK 8.5 (for Java) troubleshooting -- Invalid config file Invalid bootstrap data
2 years ago
Originally Published: 2015-12-23
Article Number
000063035
Applies To
RSA Product Set: SecurID
RSA Product/Service Type: Authentication Manager SDK for Java
RSA Version/Condition: 8.5
Issue
Auth SDK Failed on startup, log shows below
[2015-12-23 10:58:25,720] FATAL main - RSA Authentication API for Java v8.5.0.0.0[1148] started
[2015-12-23 10:58:25,736] INFO main - sdopts.rec doesn't exist
[2015-12-23 10:58:25,736] INFO main - securid doesn't exist
[2015-12-23 10:58:26,173] DEBUG main - Added JAXB context for : com.rsa.authmgr.commonagent.xsd.bootstrap
[2015-12-23 10:58:26,220] FATAL main - Exception unmarshalling type: java.lang.Class Exception: Premature end of file.
[2015-12-23 10:58:26,220] ERROR main - {RealmConfig.updateNewProtocolInfo} Invalid config file Invalid bootstrap data
Tasks
Check if customer is still using a sdconf.rec from AM 7.1 or 6.1
- The old file doesn't contain the bootstrap data (you can only see binary data).
- In new sdconf.rec, appended below info:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?><bootstrap:AgentConfiguration ConfigServiceUrl="http://${0}:${1}/Services/ConfigService" ConfigServicePort="5500" xmlns:bootstrap="http://www.rsa.com/schemas/2008/05/CommonAPI/bootstrap"><bootstrap:ServiceKeys><bootstrap:X509Certificate>MIIDmDCCAoCgAwIBAgIQm2C8VpYmDU6vYPhM9OW+xzANBgkqhkiG9w0BA
QUFADB8MS8wLQYDVQQDDCZSU0Egcm9vdCBDQSBmb3IgYXBwODFwLmNzYXUuYXAucnNhLm5l
......
></bootstrap:PoolSet></bootstrap:AgentConfiguration>
Resolution
1. Generate a sdconf.rec from AM8.1
2. Replace the existing one
3. Clear Node Secret on both agent and AM side (as in new Auth Protocol, no need to hold node secret any more, it will use certificate to encrypt/decrypt the traffic, if there's any node serct it will impact the communitcation)