Departments or units that wish to integrate applications with any UGA SSO environment (Development, Staging, or Production) must submit an integration request using the UGA SSO Integration Request Form.
Information Required in the Request Form
Application owners will be asked to provide:
- URLs for each environment: Development, Staging, and Production
- A list of identity attributes to be returned to the application
- The SSO protocol to be used: CAS, SAML, or OIDC
- If using SAML, a metadata file or metadata URL must be included
- The expected timeframe for moving the application into production
- Any application-specific requirements needed to support ArchPass (Duo multi-factor authentication)
Note: ArchPass (Duo multi-factor authentication) is required for all UGA SSO-integrated applications in accordance with University System of Georgia (USG) security requirements. Applications requiring an exception must submit a request through the Policies, Standards, and Guidelines Request Service. All exception requests are reviewed and approved by the EITS Information Security (InfoSec) Team.
Once submitted, the request initiates a workflow managed by the EITS Identity Management (IDM) Team, the EITS Information Security (InfoSec) Team, and the EITS Linux Team. The application owner will receive updates and communications through the ticketing system throughout the onboarding process.
Note: All new applications must begin in the Development environment. Applications may only advance to Staging and Production after all required testing, security reviews, and approvals have been completed.
Timeline and Review Process
Application owners should allow a minimum of eight weeks between request submission and the desired production go-live date, assuming no issues are identified during the onboarding process.
All newly registered applications are subject to a security review and vulnerability assessment conducted by the EITS Information Security Team.
Following successful testing and completion of all required reviews and approvals, the EITS Linux Team will coordinate with the application owner to schedule and confirm the production deployment date.
Testing the Integration
Testing is the responsibility of the application owner and should include:
- Verifying functionality in Development, Staging, and Production environments
- Testing after UGA SSO maintenance windows
- Testing after any application changes that may affect SSO functionality (for example, certificate updates, configuration changes, or attribute modifications)
Application owners must attest that testing has been completed successfully at designated points throughout the integration workflow.
Test Accounts
Test MyID accounts can be requested to simulate authentication and authorization scenarios. These accounts can be configured to reflect specific user populations, authorization criteria, or attribute mappings.
Request a test account using the Test MyID Checkout Form.
Application Owner Responsibilities
Application owners are responsible for:
- Serving as the primary contact for the SSO integration
- Providing timely responses to requests for information, testing, and approvals
- Signing off on successful integration testing in all environments through the integration workflow
- Coordinating with application vendors during integration and testing activities
- Notifying EITS when the application is decommissioned or no longer requires SSO access
EITS Responsibilities
The EITS SSO IDM Team, Information Security Team, and Linux Team are responsible for:
- Reviewing integration requirements and technical details
- Coordinating data classification and security reviews
- Ensuring ArchPass (Duo multi-factor authentication) is implemented for UGA SSO-integrated applications in accordance with University System of Georgia (USG) security requirements
- Reviewing and approving requests for exceptions to the ArchPass requirement (InfoSec)
- Reviewing requested attributes, SSO protocols, and implementation timelines
- Creating development configurations and other resources needed for testing
- Assisting with onboarding and configuration in Development, Staging, and Production environments
- Coordinating production deployments and confirming production go-live dates with application owners
- Maintaining, securing, and upgrading the UGA SSO platform
UGA SSO Application Listserv
All application owners are automatically subscribed to the UGASSOApps Listserv, which is used for:
- Announcements related to SSO maintenance, outages, upgrades, and service updates
- Sharing information, best practices, and questions related to UGA SSO integrations
The listserv is a community discussion forum, and messages are not moderated. Participation in the UGA SSO program includes participation in Listserv communications.
UGA SSO Maintenance Windows
EITS schedules regular maintenance windows for production SSO updates:
- Bi-monthly, after 5:00 p.m. on Fridays that coincide with the scheduled Windows and Linux server maintenance cycle
- Emergency maintenance may be performed as needed to address critical vulnerabilities, patches, or service issues
- During major platform upgrades, scheduled maintenance activities may be temporarily modified or suspended to allow application owners sufficient time to test against upgraded SSO components before production deployment