Skip to Page Content

UGA SSO

All current, active UGA web applications must migrate to use UGA Single Sign-On (UGA SSO) by March 6, 2020.

Below are the requirements for using UGA SSO and the steps for migrating applications for application owners. 

UGA SSO incorporates many existing protocols, including SAML (CAS), SAML2 (CAS2), OAuth and OpenID. For information about the transition can be found this single sign-on presentation

A project plan template is available for application owners. A schedule of maintenance windows for adding applications is also available. 

Application owners: Please make sure you have completed a project plan template and reviewed information on our authentication protocols before you submit an SSO Integration Request.

For more information, please contact idm@uga.edu .

Application owner responsibilties

  • An application owner must be listed on the SSO configuration. This application owner will be the primary point of contact for questions regarding the SSO setup for the application
  • Application owners must have a clear project plan, with testing and go-live dates. A project template is available for your use. Please submit the project plan via this form. 
  • Application owners or their designees are responsible for creating a test plan and testing their applications. This includes testing in the following scenarios:
    • Testing while the application is being added to development, staging, and production SSO environments
    • Testing after regular SSO maintenance windows
    • Testing after application changes that impact the SSO Configuration, ie certificate updates, attribute release
  • Application owners or their designees are responsible for signing off when an application works as expected in development, staging and production SSO environments.
  • Application owners must inform EITS when the application is decommissioned.

EITS responsibilities 

  • EITS will review each application project plan. 
  • Each project plan will be sent to the Office of Information Security for security review and investigation. The security review will determine the type of data that is being protected (restricted, sensitive, critical, other). The review will also determine whether the application requires ArchPass, UGA's two-step authentication solution, powered by Duo.
  • EITS will review each applications attributes, project plan dates and protocols
  • EITS will create development accounts for testing the application
  • The IDM team will work with the selected application owner to get the application in the development environment, staging environment and production environment during the appropriate maintenance windows.

UGA SSO Maintenance Windows

Development Environments

  Duration Day Time Anticipated Service Disruption
Application Maintenance 8 hours Any weekday 8 a.m. to 4 p.m. Low - Medium
System Maintenance  8 hours Any weekday 8 a.m. to 4 p.m. High

Stage Environments

  Duration Day Time Anticipated Service Disruption
Application Maintenance 2 hours Monday through Friday 3 p.m. to 5 p.m.  Low - Medium
System Maintenance  8 hours Last Wednesday of the month 8 a.m. to 4 p.m. High

Production Environments

  Duration Day Time Anticipated Service Disruption
Application Maintenance 4 hours 1st and 3rd Fridays of the month 11 p.m. to 3 a.m. Low - Medium
System Maintenance  8 hours 1st Friday of the month 11 p.m. to 7 a.m. High

Emergency maintenance will be conducted as needed.