Announcements

SecurID® Discussions

Browse the SecurID discussion board to get product help and collaborate with other SecurID users.
HarisankarCR
Beginner
Beginner

Distrubute token via self service console

Jump to solution

When a user gets a new PC  or loses their phone they need their token redistributed.  Is there a feature in self-service functionality allow the user to get token on their own with latest versions?  

Labels (1)
0 Likes
1 Solution

Accepted Solutions

It is not possible to redistribute the same token but the user can request a new token

 

Best Regards,

Ahmed Abouelnaga

View solution in original post

5 Replies
AhmedAbouelnaga
Occasional Contributor Occasional Contributor
Occasional Contributor

Hello Harisankar,

 

You can allow the users to request a new token by selecting the software tokens for provisioning as described in the below link:

Select Software Tokens for Provisioning 

 

Then configure a workflow policy as described in the below link:

Configure a Workflow Policy 

And on the Software Token page, do the following: under Workflow Definitions, specify the number of steps required for each request type to be 0 in order to allow the token to be provisioned with no Administrator interference or approvals.

 

Hope this helps.

Best Regards,

Ahmed Abouelnaga

Hi Ahmed,

 

Thanks for answering.My question was  Is it possible to redistribute the token via self service portal if end user change the device (for example they change from android to iphone or,during a PC refresh etc). and Use self service console portal to import back the token again?

It is not possible to redistribute the same token but the user can request a new token

 

Best Regards,

Ahmed Abouelnaga

HarisankarCR
Beginner
Beginner

Is it the same case with AM PRIME license ?

0 Likes
CraigDore
Frequent Contributor Frequent Contributor
Frequent Contributor

Hi Harisankar - the response above is definitely correct. Typically software tokens are distributed using a key agreement scheme in which the endpoint device contributes to the creation of the key. No lift and shift onto a new device.


If you had distributed the token via files and have the original token file (.stdid) was provided without the device binding feature enabled then it can be copied. But none of this is best practice at all.

 

On the Prime question, the answer is the same. When a user changes devices, they must go through the activation process again.

 

I hope that's clear.