UF SailPoint IdentityNow
As part of the modernization of the University of Florida’s identity and access management setup, a decision was made to move from the legacy system (Home-grown ARS system in PeopleSoft) to Sailpoint. As part of this transition, there will be a few changes to existing processes, procedures and access methods. Below you will find information as to what is changing and define some common-use terms in the new system. You can also visit our FAQ page for answers to some commonly asked questions.
Changes from ARS to Sailpoint
For the most part, the abilities currently in place for DSAs and Role approvers stay the same, with a few notable exceptions.
DSAs –
- Role requests to add access are no longer bound by departmental authority.
- Any DSA can request for any user in the UF Registry
- All requests are logged and will be carefully audited by the IAM team
- Role requests to remove access can no longer be requested by the non-primary DSA
- Annual certification will no longer be completed by the DSA.
Primary DSAs –
- New concept in Sailpoint. Primary DSAs have all of the abilities of a DSA, with a few added roles / responsibilities
- Recertifications
- Role removal requests
Role approver –
- Current abilities regarding approval stays the same
- Role approvers are assigned to specific roles to approve / deny
- Training is no longer a blocker for requests
- Role approvers are expected to check for completed training prior to approving roles
- Can now request roles
- The role approver can now request roles as a DSA can (not primary DSA).
- Role approvers cannot approve roles they request
- Recertification
- Role approvers will be responsible for re-certification of roles that have been approved on some regular interval for high-impact or high-security roles.
For questions, please reach out to the Identity team via: ufit-ars@ad.ufl.edu
Below is an information session related to the upcoming transition from PeopleSoft ARS to Sailpoint Identity Management
Download the PDF here
