Authentication

Authentication refers to the method that students and teachers will use to login to the tool. All tools that store/collect data must meet the authentication requirements outlined below.

Why is this a requirement?

• Instructional time is valuable - Authentication ensures that students and staff can quickly login to the tool, which allows for a smooth onboarding and allows teachers to spend more time on learning and less time managing individual usernames and passwords.
• Safeguard our data - We value the privacy and security of our student & staff data, which is why strong authentication is a critical tool with all software & online tools.

What is preferred?

Google Authentication - This can be accomplished via Google login or SAML authentication. If Google is used for sign-in, there can not be alternative pathways to authenticate (i.e. forgot password link).

Clever - Authentication through Clever allows students and staff to quickly access an application through our Clever portal. Please note that Clever SSO does not require an application to be rostered through Clever.

What is accepted?

SAML - Authentication using SAML is also accepted, although it is preferred that SAML be configured to use Google if possible.

Active Directory - Authentication through AD can be enabled using Azure AD.

What is prohibited?

Standalone Accounts - The use of separate accounts where students & staff must set a unique password and use a "forgot password" link to reset their account is prohibited. Standalone accounts do not provide adequate data security and create an unnecessary burden on our school and central staff.