Enabling Multiple Tokens (Sun Identity Manager 8.1 Resources Reference)

Sun Identity Manager 8.1 Resources Reference

Enabling Multiple Tokens

The default schema map for both SecurID resource adapters is set-up to allow the administrator to specify one token. If you are using the SecurID User Form provided in the InstallDir\samples\forms directory, perform the following steps to enable up to three tokens.

Enabling up to Three Tokens

Edit the following section of the SecurID User Form:

<FieldLoop for=’tokenNum’>   <expression>      <ref>oneTokenList</ref>   </expression>

Change oneTokenList to threeTokenList.

Load the User Form into Identity Manager.

Rename the following Identity Manager User Attributes on the left side of SecurID ACE/Server schema map:

Original Identity Manager User Attribute	Renamed Identity Manager User Attribute
`tokenClearPin`	`token1ClearPin`
`tokenDisabled`	`token1Disabled`
`tokenLost`	`token1Lost`
`tokenLostPassword`	`token1LostPassword`
`tokenLostExpireDate`	`token1LostExpireDate`
`tokenLostExpireHour`	`token1LostExpireHour`
`tokenLostLifeTime`	`token1LostLifeTime`
`tokenPinToNTC`	`token1PinToNTC`
`tokenPinToNTCSequence`	`token1PinToNTCSequence`
`expirePassword`	`token1NewPinMode`
`password`	`token1Pin`
`tokenResync`	`token1Resync`
`tokenFirstSequence`	`token1FirstSequence`
`tokenNextSequence`	`token1NextSequence`
`tokenSerialNumber`	`token1SerialNumber`
`tokenUnassign`	`token1Unassign`

Add the following fields to the schema map to accommodate a second token:

Identity Manager User Attribute	Resource User Attribute
`token2ClearPin`	`token2ClearPin`
`token2Disabled`	`token2Disabled`
`token2Lost`	`token2Lost`
`token2LostPassword`	`token2LostPassword`
`token2LostExpireDate`	`token2LostExpireDate`
`token2LostExpireHour`	`token2LostExpireHour`
`token2LostLifeTime`	`token2LostLifeTime`
`token2NewPinMode`	`token2NewPinMode`
`token2PinToNTC`	`token2PinToNTC`
`token2PinToNTCSequence`	`token2PinToNTCSequence`
`password`	`token2Pin`
`token2Resync`	`token2Resync`
`token2FirstSequence`	`token2FirstSequence`
`token2NextSequence`	`token2NextSequence`
`token2SerialNumber`	`token2SerialNumber`
`token2Unassign`	`token2Unassign`

Add the following fields to the schema map to accommodate a third token:

Identity Manager User Attribute	Resource User Attribute
`token3ClearPin`	`token3ClearPin`
`token3Disabled`	`token3Disabled`
`token3Lost`	`token3Lost`
`token3LostPassword`	`token3LostPassword`
`token3LostExpireDate`	`token3LostExpireDate`
`token3LostExpireHour`	`token3LostExpireHour`
`token3LostLifeTime`	`token3LostLifeTime`
`token3NewPinMode`	`token3NewPinMode`
`token3PinToNTC`	`token3PinToNTC`
`token3PinToNTCSequence`	`token3PinToNTCSequence`
`password`	`token3Pin`
`token3Resync`	`token3Resync`
`token3FirstSequence`	`token3FirstSequence`
`token3NextSequence`	`token3NextSequence`
`token3SerialNumber`	`token3SerialNumber`
`token3Unassign`	`token3Unassign`