- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Account Active time
Hello
We have 2000+ rotating students during the year. Of those students maybe 55 of them needs RSA ODA authentication in a month and each month those 55 students change, at the beginning of the year we know which students need access when, so without wasting 605 RSA licenses or having someone manually change the accounts each month is there a way schedule access.
Example:
September: students1, 2,3 need access
October: students 4,,5,6 need access and students 1,2,3 are to be removed.
November: students 7,8,9 need access and students 4,5,6 are to be removed.
Thanks
Wesley
- Tags:
- CAS
- Cloud
- Cloud Auth
- Cloud Authentication
- Cloud Authentication Service
- Community Thread
- Discussion
- Forum Thread
- RSA SecurID
- RSA SecurID Access
- SaaS
- SecurID
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
You can schedule a users access to authentication agents based on date and time, but not schedule who is enabled for on-demand or otherwise 'taking a slot' from the license. You'll need to hand-administer these monthly scenarios accordingly.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
This can also be managed using the AM "Bulk Administration" (AMBA) interface. There is a "DODA" ("Disable On Demand Authentication") control that can be used to disable large sets of users. This functionality is detailed in the RSA® Authentication Manager 8.2 Service Pack 1 Bulk Administration 1.6.0 Custom Application Guide (DOC-54026).
It is also possible to create accounts that expire. When creating a user, the "Account Information" section has controls for "Account Starts" and "Account Expires" settings. Expired user accounts should not be counted against your license.
