Child pages
  • LSChromeFilter SSO Setup
Skip to end of metadata
Go to start of metadata

Setting up Google as an Authentication source for your Rocket/Web Filter will allow users to seamlessly sign on to their Chromebook devices and Google services with their Web Filter policies. GAFE Single Sign On (SSO) can be set up by following the steps below to configure Google as an authentication source.

Note:

The way Google authentication works it can be used for personal overrides but not the “teacher override” where the override is performed for another user.

Configuring a Google authentication source

Note: This procedure requires Lightspeed System Rocket release 2.7.0rc3 or later.

Configure the Google Web App

Click Go to My Console

    • 4. Click Create Project.

google-cloud-console

    • 4. Enter a project name.

create-new-google-project

    • 5. A project ID will be generated automatically. As an option you can enter your own project ID.
    • 6. Check (select) I have read and agree to all Terms of Service for the Google Cloud Platform products.
    • 7. Click Create.
    • 8. Click APIs & auth.

apis-and-auth

    • 9. Click APIs.

Click APIs

    • The following window to enable the Admin SDK APIs will be displayed.

enable-the-admin-sdk

    • 10. Check (select) I have read and agree to both Google APIs Terms of Service and Google Apps Admin APIs Terms of Service.
    • 11. Click Accept.
    • 12. Click Credentials.

click-credentials

Note

Make sure that your project has a product name under APIs & Auth -> Consent screen. If the name is missing, you will either see 'Error: disabled_client' or 'Error: invalid_client' when adding the authentication source.

    • 13. Click Create New Client ID.

create-client-id

    • 14. Check (select) Web Application.

create-web-application

Note:

Redirect URLs must be HTTP and not HTTPS.

    • 15. In the Authorized redirect URL field enter the redirect URL. Please note that this URL must be the publicly-available hostname of your Rocket with an ending suffix of /auth/google_oauth2/callback (for example, http://your-rocket.com/auth/google_oauth2/callback).

 

client-id-and-secret

    • 16. Click Create Client ID.
    • 17. Copy the Client ID and Client Secret, which you will need when configuring the Google authentication source on the Rocket (described below).


This will complete setup of the Google web app.

Enable API Lookups for the Google Domain

click-on-security-icon

    • 3. Click API reference.

click-api-reference

    • 4. Under API access check (select) Enable API access.

enable-api-access

This will complete setup on the Google side.

Configure a Google Authentication Source on the Rocket Appliance

    • 1. Log in to the Rocket.
    • 2. Click Administration.
    • 3. Scroll down to Authentication Sources.
    • 4. Perform Steps a through g for every tier.
      • a. Click Add Authentication Source.

add-google-auth-source

      • b. From the Type dropdown select Google Authentication.
      • c. Enter a name, a friendly name, and the email domain (everything after the @ sign).
      • d. Enter the Client ID and Client Secret you copied above.
      • e. Select (check) Available to End Users.
      • f. Click Save. You will be directed back to Google to give them permission to make API calls. Please note that all “scopes (i.e., authentication information received from users) listed on this window are read-only.

google-api-calls

Note:

You must be logged in as an administrator of your Google domain. It will look like everything was setup fine, however, the auth source just won’t work. A client accessing this will either get a 401 Unauthorized or 403 Forbidden when attempting to use the auth source.

    • g. Click Accept
  • No labels