Clevr Authentication Google SSO

Clevr Authentication Google SSO

Google SSO

Before configuring Google SSO in Clevr the client must first setup Google SSO using the instruction on https://support.google.com/a/answer/6087519. As part of the configuration the customer will be prompted to provide the ACS URL and Entity ID in the Service Provider Details dialog.

Service Provider Details

The service provider details for clevr are: 

Canadian Cloud (www.clevrcloud.ca) 

Entity ID: https://www.clevrcloud.ca:443 

ACS URL: https://www.clevrcloud.ca/clevr/SAML/SSOConsumerService.aspx 

Logout URL: https://www.clevrcloud.ca/clevr/SAML/SLOService.aspx 

Start URL: https://www.clevrcloud.ca/clevr/SSOLogin.aspx?SSOTenant=[TenantID] 

US Cloud (www.clevrcloud.com) 

Entity ID: https://www.clevrcloud.com:443 

ACS URL: https://www.clevrcloud.com/clevr/SAML/SSOConsumerService.aspx 

Logout URL: https://www.clevrcloud.com/clevr/SAML/SLOService.aspx 


Once the Service Provider details are configured the client must configure the Attribute Mapping in Google to expose the First Name, Last Name and email.



In order to authenticate to the new clevr service users that need access to cCevr have to be added to the new Clevr service in Google.
After Google SSO has been configured by the client the following is required to configure clevr Google SSO:
  1. URL to the Google metadata
or
  1. SSO Endpoint 
  2. Sign-in Page URL 
  3. Certificate string 
  4. Parameter lists (attributes. Eg. First Name , Last Name, mail)

The final requirement is to provide Clevr with a test account to be used to validate the connection. Please provide the details when submitting information about the Service Provider settings. 


Note: Once the settings are applied the servers need to cycle overnight to refresh the configuration on the site. The settings will take effect the following day at 5am. 

Checklist

  1. Document sent to client 
  2. New Google Service application for clevr has been created by the client 
  3. Site Metadata or site information provided by the client 
  4. Test account provided by the customer 
  5. Site configured by Clevr 
  6. Validate configuration and authentication using a few users 
  7. ​Clevr authentication using Google SSO rolled out to all user

    • Related Articles

    • Teachers with Last Years Classes

      It's expected that teachers will have last year's student lists or no students until the first day of class / class start date as defined in your Student Information System. Once the class start date is here they will be updated in Clevr with the ...