Hello,
Not sure when the defect started.
You can downgrade to a version where SSTDT worked with SSD and you do not define a profile, you define everything about the token inside the SSTDT directives.
Or maybe you can just swap to an older jar file**, and not downgrade the system, just set up a temporary 8.3.0.0.0 primary somewhere to copy it's AMBA jar file.
------------------
This example is what I mean. Deploy a pinless 8 digit software token that is already assigned to a user. This has zero to do with any software token profile, only the device type name and FamilyKey matters.
Action,Key,KeyType,Miscvariable
SSTDT,Android,FamilyKey,1.x
CIF,Action,TokSerial,PINType,TokEnabled,OTPLength,DeliveryMethod,DestinationAddress
SSD,000020735716,tokencode,1,8,SMTP,administrator@farmco.local
This will fail in the current version as the newest SSD requires a profile to be defined.
Some of it works, as part the underlying code is the same
-Entering CommandUtils.setSoftTokenDeviceType
Info : -Key: keyType = Value: FamilyKey
Info : -Key: Linenumber = Value: 2
Info : -Key: Action = Value: SSTDT
Info : -Key: MiscVariable = Value: 1.x
Info : -Key: key = Value: Android
<snip>
But then problems with SSD
-applyTokenSettings(...) - Key: Linenumber = Value: 4
Info : -applyTokenSettings(...) - Key: Action = Value: SSD
Info : -applyTokenSettings(...) - Key: DestinationAddress = Value: administrator@farmco.local
Info : -applyTokenSettings(...) - Key: PinType = Value: tokencode
Info : -applyTokenSettings(...) - Key: TokEnabled = Value: 1
Info : -applyTokenSettings(...) - Key: OTPLength = Value: 8
Info : -applyTokenSettings(...) - Key: DeliveryMethod = Value: SMTP
Info : -applyTokenSettings(...) - Key: TokSerial = Value: 000020735716
Failure: 2018-12-12 09:21:23 : Line 4 - singleSofttokenDeployment -Token 000020735716 not deployed. Reason: Software Token Profile is required to deploy software token
8.3.0.3.0 will also fail because this is where defining software token profiles by name started.
---
My csv example above, it may (should) work in 8.3.0.2.0 and earlier. The downside is that when you view the token it will have blank as a software token profile name since you are not defining a profile, you are building the whole token inside AMBA.
**You can try just replacing the /opt/rsa/am/utils/lib AMBA jar file with a version from 8.3.0.0.0 base, but I have never tested this swap.... and am not set up to do so. It's pretty harmless to test it, just rename the current jar to preserve a copy (AMBulkAdmin-8.3.0.5.0.jar-bak)
Bring over a copy from 8.3.0.0.0, and rename it to match the current version if you try it, then test my CSV example above...if it runs you should get pinless tokens.
/opt/rsa/am/utils/lib/AMBulkAdmin-8.3.0.5.0.jar (renamed from AMBulkAdmin-8.3.0.0.0.jar)
