Specifications include, but are not limited to: 1. The system should integrate with current University authentication services and protocols. 2. The system should integrate with university institutional information for user account and profile provisioning and de-provisioning (create, update, and delete operations). 3. The system should integrate with existing University services to manage groups, roles, and permissions. The system’s access control model should be flexible and extensible by the University as required to meet business needs. 4. The system should allow configuration of user session controls that meet University security and privacy needs including dual authentication. User controls will not be limited to HCM-based hierarchy but can be configured within tool. 5. The system must be able to encrypt all web access (HTTPS). 6. The system should allow users to have multiple roles without requiring multiple login accounts. The number of users is unknown and will vary.
