Whenever a student starts a new browsing session at home, they are required to log in to Google or Azure AD to allow Securly to capture user-specific activity. This is essential to generate student-specific reports and help teachers act upon flagged activities accurately.
Before Securly launched Azure AD authentication support, a student was displayed on the standard Google 'Choose an account' page. But with Azure AD available to schools, a new page with two login options is displayed.
How does this impact your login behavior?
1. Depending upon the authentication mechanism used by the school, the student should select either 'Login with Google' or 'Login with Microsoft Azure AD'.
2. If the student selects 'Login with Google' they will be directed to the Google 'Choose an account' page from where they can log in to their Google account.
Students can log into their Google or Azure AD accounts using these two simple steps and stay protected from inappropriate content and cyberbullies on the internet.
Resolving authentication conflicts between Azure AD and Securly Filter
Some students may experience authentication conflicts when accessing Microsoft or Google services on home WiFi. This can happen when the device or browser has cached credentials that conflict with the school's Securly Filter policy. Follow the steps below to resolve these issues.
Step 1: Clear the DNS cache
A stale DNS cache can cause authentication redirects to fail. Clear the DNS cache on the device before attempting to log in again.
Step 2: Authenticate with the school domain first
Before accessing Microsoft or Google services, log in using the school-issued account (e.g., the Azure AD or Google Workspace account provided by the school). This ensures Securly Filter recognizes the session correctly.
Step 3: Verify Forced Login is active in the take-home policy
Admins should confirm that Forced Login is turned on in the take-home filtering policy in Securly Filter. Without this setting, students may bypass the login prompt, causing session and authentication conflicts.
Step 4: Add the secondary domain to Google login restrictions (for Google services)
If students use a secondary Google domain (e.g., a personal Gmail account alongside a school account), add that secondary domain to the Google login restrictions in Securly Filter. This prevents conflicts when Google services detect multiple accounts.
Step 5: Clear the browser cache
If the above steps do not resolve the issue, clear the browser cache and cookies, then attempt to log in again. Cached session data can interfere with the authentication flow.
Step 6: Add GroupMe-related domains to the Global Allow list
If students are experiencing issues specifically with GroupMe or related Microsoft services, add all GroupMe-related domains to the Global Allow list in Securly Filter. This prevents the filter from blocking authentication requests from those services.
If issues persist after completing all steps, contact Securly Support for further assistance.
Comments
Article is closed for comments.