---
title: "SSO Outage Considerations and Application Access Requirements"
canonical: "https://kb.uconn.edu/space/IKB/28320759834/SSO%20Outage%20Considerations%20and%20Application%20Access%20Requirements"
format: markdown
---
## Overview

Single Sign-On (SSO) is a critical dependency for many UConn applications. When SSO is unavailable, application accessibility depends on whether the application has an approved alternative access method. This article outlines expectations, risks, and requirements related to SSO outages and non-SSO access.

## When SSO Is Unavailable

If SSO is down and an application relies exclusively on SSO for authentication, **the application will be inaccessible** for the duration of the outage. There is no workaround in this scenario.

Application owners should understand this risk and factor it into business continuity planning.

## Applications with Alternative (“Backdoor”) Accounts

Some applications include local or non-SSO administrative accounts intended for emergency or break-glass access. While these accounts may allow limited access during an SSO outage, they introduce additional security considerations.

### Security Requirements for Non-SSO Accounts

Any alternative or local account **must comply with UConn security standards**, including but not limited to:

- **Multi-Factor Authentication (MFA)**    
MFA is required, even for emergency or administrative accounts.
- **Password Standards**    
Passwords must meet UConn minimum requirements for:
  - Length
  - Complexity
  - Rotation (if applicable)
  - Secure storage and handling
- **Access Control**
  - Accounts should be limited to the minimum number of users necessary
  - Use should be documented and auditable
  - Credentials must not be shared informally

### Ownership and Responsibility

The **application owner** is responsible for:

- Ensuring any non-SSO accounts meet UConn security policy
- Documenting the purpose and use of such accounts
- Reviewing and validating continued need on a regular basis

## Recommendations

- Applications support SSO as the primary authentication method
- Clearly understand the operational impact of SSO outages
- Avoid unmanaged or undocumented “backdoor” accounts
- Engage Identity and Access Management (IAM) early when evaluating authentication designs

## Questions or Assistance

For guidance on SSO dependencies, MFA requirements, or acceptable emergency access patterns, contact the UConn Identity and Access Management team.