Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

This article will layout the steps to take to setup to ClassLink, Clever or Microsoft SSO.

Prerequisites

Organizations using ClassLink, Clever or Microsoft as authentication providers have an internal Service Administrator, that is known as the ClassLink Administrator, Clever Administrator or Microsoft Administrator. This person controls the users and applications within their organization on that authentication provider.

The following diagram shows the process to change the authentication method for a District:

\uD83D\uDCD8 Instructions

  1. The Service Administrator has to enable the http://CLIEngage.org application and define the type of users that would be able to use it through that portal or dashboard. This step authorizes their system to send user credentials to CLI Engage when login in using that method.

  2. The District will select at least an administrator and a teacher for testing login with the new authentication provider.

  3. CSA from CLI will transform the tester accounts to the new authentication provider and send a new invitation to register again. Login problems will be resolved with the assistance of the Service Administrator.

  4. The testers will complete the registration steps.

  5. The testers will complete their testing by navigating through the Assessment, Online Courses and Administrative pages. the District will announce to their users the login method change.

  6. The District will announce the Go-Live date to all their users.

  7. CSA will make the Authentication Method change at the Community page https://cliengage.org/Community/Community/Index
    a. The CSA will compile a list of Users and will provide it to the Database Analyst to transform all the user accounts. This list needs to be created using the Export tool in Engage https://cliengage.org/Export/Export/Index
    b. The Database Analyst will run the script to trigger new invitations for every user, active and inactive ones. This step will ensure that the District will not keep any user registered with the old type of credentials.

  8. The CSA will inform the District Administrators that the transformation process has been completed.

If you need further assistance, please submit a help ticket.

  • No labels