Single Sign-On (SSO) enables users to access multiple TU applications securely with one familiar login. SSO is mandatory for apps containing PII or financial data. OTS supports SAML, OAuth2 and OIDC login methods via Microsoft Entra ID (formerly Azure AD.) Vendors that are members of the InCommon Federation may require minimal configuration to enable SSO. Applications utilizing OAuth2 or OIDC may require additional security review. Although initial setup requires considerable collaboration between OTS and the application owner, ongoing maintenance is minimal.
To process your request, the application owner should submit a ticket to OTS and provide:
- Application and website name
- Any existing Towson-specific URLs or addresses
- SSO configuration documentation from the vendor (links or support docs)
- Details on current TU community usage and user profiles
- Information on roles within the application
- User addition and removal process
Each application has unique requirements, offering various options for SSO configuration. Effective communication among the application owner, OTS, and the vendor is necessary to ensure the setup is secure and accessible.
Still need help? Consider the Related Articles box on this page or
Open a Ticket.
Use the
Yes or
No button below to provide feedback on this article. Please provide any details on what you liked and what may need improvement.