- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
AMBA ATU assign tokens issues: OTPLength not accepted
I'm new to AMBA and getting some issues during tokens assignment to AD users. AD users already exist/provisioned to RSA AM, I need just to assign Soft tokens to them.
Here is my CSV file:
Action,IdentitySource,DefLogin,TokSerial,ReplTokSerial,TokEnabled,DeviceSerialNumber,Nickname,ProfileName,OTPLength |
ATU,AccessVDI,spbdudkia,,000239075954,1,a01c4380-fc01-4df0-b113-7fb98ec74694,Android,,6 |
1) The first error I get is that OTPLength parameter is not accepted while the token itself is successfully assigned
Error : 2017-03-23 12:04:44 : Line 2 - addTokenToUser -Token 000239075954, not deployed. Reason: Cannot create softID file for token 000239075954 assigned to SPBDUDKIA. Error: Requested length <SIX_DIGITS> not allowed for device type null
Failure: 2017-03-23 12:04:44 : Line 2 - addTokenToUser -Token 000239075954 assigned but not deployed to spbdudkia. Reason: Cannot create softID file for token 000239075954 assigned to SPBDUDKIA. Error: Requested length <SIX_DIGITS> not allowed for device type null
The generic AES token is assigned with 8 digits passcode after that that is not licked to any device type (though I specified DeviceSerialNumber for Android). At the same time when I assign token via IWS it is assigned with 6 digits because I'm able to apply Software token profile specifically for Android or iOS.
2) Second is that DeviceSerialNumber,Nickname are ignored and not assigned to the token (no issue in output and the fields of the token are empty when I check via IWS)
3) I can't assign token profile to the tokens. I have several Software token profiles configured in IWS.
I tried both via ATU and AP command but get the same result:
2 - assignProfile -spbdudkia, CTF-Android-60-6-PiNPad API return: Principal Not found
My AP csv file is:
Action,DefLogin,ProfileName
AP,spbdudkia,CTF-Android-60-6-PiNPad
Your advices are much appeciated
- Tags:
- AM
- AMBA
- assigning tokens
- Auth Manager
- Authentication Manager
- Authentication Manager Bulk Admin
- Community Thread
- Discussion
- Forum Thread
- RSA Authentication Manager
- RSA SecurID
- RSA SecurID Access
- SecurID
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Quick answer on number 3 from documentation:
"If ―DefLogin‖ is given as input, and if Security Domain and Identity Source are not provided, then the user will be searched in the default identity source (Internal DataBase)"
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Barbour,
thank you for this quick answer, true, after setting up IndetitySource it changed to another issue:
2 - assignProfile -spbdudkia, CTF-Android-60-6-PiNPad API return: Profile CTF-Android-60-6-PiNPad not Found
Action,DefLogin,ProfileName,IdentitySource
AP,spbdudkia,CTF-Android-60-6-PiNPad,AccessVDI
Am I right that these profiles that I can set here are the same Software token profiles that I configure via IWS?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I believe the AP command is actually referring to RADIUS profiles.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I was able to find the answer for 1 and 2 questions by myself. Before using ATU command the device type must be defined for the token in SSTDT command.
Then you need to use CIF to change the fields before using ATU.
Now my working csv looks like:
Action,Key,KeyType,MiscVariable |
SSTDT,Android,FamilyKey,2.x |
CIF,Action,IdentitySource,DefLogin,TokSerial,ReplTokSerial,TokEnabled,DeviceSerialNumber,Nickname,ProfileName,OTPLength |
ATU,AccessVDI,spbdudkia,,000239075954,1,a01c4380-fc01-4df0-b113-7fb98ec74694,Android,,6 |
