SSO integrations overview

SchoolDay SSO lets users sign in once through your district's identity provider (IdP) and access all connected applications automatically. No separate credentials are needed per app.

SchoolDay uses SAML (Security Assertion Markup Language) to verify identity and pass access securely between your IdP and each application.

What is SSO integration?

SSO integration establishes a trust relationship between three entities:

• Identity Provider (IdP): Your district's authentication system (Google, Azure AD, ADFS, or Active Directory). It maintains the user directory and authenticates users.
• SchoolDay: The service provider that facilitates communication between your IdP and applications.
• SSO applications: Third-party tools that SchoolDay connects to your IdP.

This trust is established through an exchange of SAML (Security Assertion Markup Language) metadata and digital certificates. The metadata tells each system how to communicate securely with the others.

How SSO authentication works

SchoolDay Single SSO authenticates users once through your district's identity provider, then grants them automatic access to connected applications without entering additional credentials.

The authentication flow:

1. User signs in to SchoolDay through your district's IdP (Google, Azure AD, ADFS, or Active Directory).
2. SchoolDay verifies the user's identity with the IdP.
3. SchoolDay creates a session token for the authenticated user.
4. User clicks an app icon in the SchoolDay Portal.
5. SchoolDay sends the session token to the app.
6. The app logs the user in automatically (no additional login prompt appears).

Set up SSO in SchoolDay

Next steps

• Add an SSO application
• Change SSO application assignments
• Test an SSO application