000029116 - DPM: Unable to register more than one token server using the same auto-registration profile

Document created by RSA Customer Support Employee on Jun 14, 2016Last modified by RSA Customer Support Employee on Apr 21, 2017
Version 3Show Document
  • View in full screen mode

Article Content

Article Number000029116
Applies ToRSA Product Set: Key Manager
RSA Product/Service Type: Key Manager Appliance/Server, Key Manager Token Appliance/Server
RSA Version/Condition: 3.2.x, 3.5, 3.5.1, 3.5.2
Platform: Other
Platform (Other): 3.2, 3.5
O/S Version: Other
Key Client Settings updated successfully!  Connection to key server failed
Enroll the first token server to the key server.  It will succeed and you'll notice in the client application log that its Originator originId and appNAME will match that of the failed enrollment of the second token server. 
If more than one token server is using the same auto registration profile and using the same enrollment ID name the originator information will not be unique.
In the token-only server application log:
Originator successfully retreived from local store, with the following details: originId=<THIS_SHOULD_BE_UNIQUE>,appNAME=<THIS_SHOULD_BE_UNIQUE>
WorkaroundCreate a new auto-registration profile per each token server.