Google Classroom Integration CiU

Introduction

This document will walk you through setting up your Christ in Us integration with Google Classroom. These instructions require Admin access to the Google Organization for the students and teachers using Christ in Us.  Before you start, please check you meet the following prerequisites:

  • You have admin rights to your Google Admin console and Developer console.
  • Christ in Us has been purged of previous school years’ users and data. Click here for more information.
  • Your Christ in Us administrator account is set up with your Google Org Email address as your username.

Section 1 - Single Sign-On App Setup

  1. Go to http://admin.google.com
  2. Click the Apps tile. 
    		3.
  3. Click the SAML Apps tile. 
    If a message pops up stating, “App management is moving,” click the “Got It” option.
    		4.


  4. Click “Add App" and select "Add custom SAML app."
    		5.
  5. Enter the application name. We recommend Christ in Us. You can add an icon image and click here to download the file.
  6. Click the “Download Metadata” button. In Section 3, you will upload this file to Christ in Us.
  7. In the Service Provider Details, enter the following: On the Attribute Mapping screen, click Finish.
    8. ACS URL:
    https://christinus.com/saml20/acs.html
    Entity ID: https://www.christinus.com
    Start URL:   Leave this Blank
    Signed Response: Check this box
    Name ID Format: EMAIL
    Name ID: Select the “Basic information and Primary Email” option.
    Click Continue
  8. On the Attribute Mapping screen, click Finish.
  9. Click “User access.”
    		10.
  10. Change Service status to “On for everyone.”
    		11.

Section 2 - API Client ID and Secret Setup

Go to https://console.cloud.google.com/ and log in as the Google admin.

  1. Click the Project button.
    2. The label of the button will be specific to your organization.
  2. Click New Project.
    		3.
    If you do not see an Organization or Location in step 3 below, please visit https://cloud.google.com/resource-manager/docs/creating-managing-organization for more information.
  3. Give your project a name. We recommend ChristinUs.
    Review the Organization and Location for accuracy and click Create.

    If you receive an error that the project could not be created, return to the Admin -> Apps -> Additional Google Services and choose Google Cloud Platform.  Project Creation Settings needs to be enabled to Allow users to create projects.
    		4.
  4. Make sure the new project appears in the menu at the top of the screen and click the APIs and Services tile under Quick Access.
    		5.
  5. Choose Library from the left hand navigation menu.
    		6.
  6. Search “Classroom” in the search bar.
    7. Click the Google Classroom API result and enable.
  7. Return to the library(see step 6 for navigation).  Search “Admin” in the search bar.
    8. Click the Admin SDK API result and enable.
  8. Return to the project page and click the API's and Services tile under Quick Access.  Then choose OAuth consent screen from the left hand navigation menu.
    		9.
  9. On Overview, click Get Started. If there is no Get Started button, choose "Branding" in the left hand navigation menu and skip to Step 12.
    		10.
    Project Configuration

  10. The following information will set up your project with settings specific to Sadlier Connect:

    Enter App name and support email address and click Next.

    For Audience, choose Internal.

    Enter your contact email.

    Agree to the terms and click Create.
    		11.
    App Domain

  11. On the Google Auth Platform page, click Branding in the left hand navigation.
  12. Upload the Christ in Us app logo.
  13. Under App domain enter the following:
    14. Application home page:
    https://sadlierconnect.com/home.html

    Application privacy policy link: https://sadlierconnect.com/privacypolicy.html

    Application terms of service link: https://sadlierconnect.com/termsandconditions.html
    Authorized Domains
  14. Click the + Add Domain button and enter sadlierconnect.com.
  15. Enter the email address(es) to which you want notifications to be sent.  Click Save and Continue.
    		16.
  16. Click Clients in the left hand navigation menu and Choose +Create Client at the top of the window.





  17. On the Create OAuth client ID window choose Application type Web Application and enter a name.





  18. Leave Authorized JavaScript origins blank.  Click +Add URI under Authorized redirect URIs and enter:

    https://christinus.com/google-classroom-redirect-login.html
  19. Click Create.
  20. On the OAuth Client confirmation page, Download the Json File.

    		21.
    Scopes

  21. Click Data Access on the left hand navigation menu and click Add or Remove Scopes.
  22. Ensure all scopes are listed by changing the default list view from 10 to 100. Choose the following non sensitive scopes:
    ../auth/userinfo.email
    ../auth/userinfo.profile
    openid
    ../auth/classroom.courses.readonly
    ../auth/classroom.coursework.students
    ../auth/classroom.rosters.readonly
    ../auth/classroom.course-work.readonly
    ../auth/classroom.student-submissions.students.readonly
    ../auth/classroom.student-submissions.me.readonly
    ../auth/classroom.coursework.me
  23. Choose the following sensitive scope: ../auth/classroom.profile.emails.
  24. Click Save.
    		25.
  25. Choose Clients from the left hand navigation menu.
  26. Use the Copy icon to copy the Client ID
    		27.

Section 3 - Configure New App Security

You will need the copied Client ID from Section 2, step 23.

  1. Return to the Admin Console at https://admin.google.com/.

  2. Click on the Security tile.
    		3.


  3. Scroll to the bottom of the page and click on the API Controls tile.
    		4.


  4. Click the Manage Third-Party APP Access link.
    		5.

  5. Click the + Add a Filter button and select App Name. Enter "ChristinUs" (without the quotation marks) for the search and click the Apply button.

    If you find the app listed, skip to Section 4. If it is not found, continue in this section with step 6.
    		6.


  6. Click Configure New App and select  OAuth App Name or Client ID,
    		7.


  7. In the search, past the Client ID obtained in Section 2, step 23. Click the Search button.
    		8.


  8. Select the Christ in Us App using the Select button that appears to the right when you mouse over it.
    		9.

  9. Check the box next to the Client ID and then the Select button in the lower right corner.
    		10.

  10. Select Trusted and clicked the Configure button.
    		11.


Section 4 - Enabling SSO in Christ in Us

  1. Log in to christinus.com with your Admin Account.
  2. Click the Click the menu button in the top left corner. Select Settings and choose Manage Google Classroom.
    		3.

  3. Change the status from Disabled to Enabled.
    		4.
    Under Setup, select “Enable Single Sign-on and Rostering” on the right.

  4. Click Choose File on the left. Upload the file you downloaded in section 1, step 6, named GoogleIDPMetadata by default.
    		5.
  5. Click Choose File on the right. Upload the JSON file downloaded in section 2, step 30 with client_secret in the name. Click Save.
    		6.
  6. Click the menu button in the top left corner. Select Settings and choose Manage Administrators.

  7. If your username is not your Google Org email address, click the ellipsis button under Actions and select Edit Account from the options. Edit the Username to be your Google organization email address.
    		8.

  8. At the top of the screen, click the down arrow next to your name to log out.
    		9.

Testing the App

We recommend testing the login from the Google App Menu using an incognito window.
The keyboard shortcuts to open an Incognito window are: 

Windows, Linux, or Chrome OS: Press Ctrl + Shift + n. 

Mac: Press ⌘ + Shift + n.

Go to the Google Waffle App Menu. You can find it on any Google website in the top right corner next to your user account icon.
The Christ in Us icon looks like the icon shown on the right.

You will land on the Christ in Us home page and not be prompted to log in.

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.