2022 - New Transition Plan
This document is attempting to show a high-level ordering of event’s to transition usesr of the Developer Portal/Apigee to use (a) SSO Integration and (b) Teams.
Title | Description | Resources | Status / Complete Date |
|---|---|---|---|
New User Creation |
|
|
|
USR-1 - Add to Google Email Group | When a new user is created, the Drupal can reach out to Google Groups and add them into api-consumer@developer.ucsb.edu automatically. | todo | |
USR-2 - Add Appropriate Drupal Roles | When a new user is created, have the new account automatically added to the Developer and/or Student roles |
| done |
Ensure SSO Integration Transition |
|
|
|
SSO-1 - Implement CAS Module | Setup the site to handle SSO/CAS logins | in progress | |
SSO-2 - Develop Documentation | Documentation for:
| todo | |
SSO-3 - Everyone should be able to log in with their SSO account and have it connect to their “old” account | To do this we need to, for all users:
a) For users with @ucsb.edu email addresses, this will be very easy. Essentially, only the Allow user to log in via CAS checkbox needs to be checked; the CAS Username field will already be populated correctly. b) For all non-@ucsb.edu email addresses (~26 accounts), we will need to check the Allow user to log in via CAS checkbox and hand populate the CAS Username field. Mike Nesbit has mapped all the non-@ucsb.edu email adddress to ucsbNetId’s in the attached ucsb-developer-20220708T190710_783Z speadsheet. Would this occur after the SSO Update on the Prod site? c) For @ucsb.edu accounts that aren’t using their actual ucsbNetId, we’ll need to update the CAS Username field by hand to the actual value. But, Elda thinks she may be able to do this programmatically. |
| in progress |
SSO-4 - Develop Communication | Develop a sample email which will be sent to users prior to the update explaining the goals and what actions they may need to take. |
| todo |
|
|
|
|
|
|
|
|
|
|
|
|
