Single Sign-On (SSO)

Single Sign-On with IMS Global Learning Consortium's Learning Tools Interoperability (LTI) Standard

If your district uses a learning platform that is compliant with Learning Tools Interoperability® (LTI), you can access Destiny resources and links without ever signing in to Destiny.

Leveraging the LTI standard supports seamless integration and single sign-on access to Destiny and Destiny resources from compliant K–12 learning platforms, such as learning management systems, portals and dashboard providers.

For background information on the LTI specification, visit: https://www.imsglobal.org/activity/learning-tools-interoperability

To generate LTI configuration information, log in as the Destiny Administrator, and then complete the following steps:

Click here for instructions

1. From the District page, click Setup.
   
2. Next to the district name, click .
   
3. In the SSO Configuration section, click Configure.
   
4. On the Single Sign-On Configuration page, click New.
   
5. From the Strategy drop-down, select lti. The Key, Secret and Endpoint fields are populated automatically.
   
6. In the Name field, type a name of your choice.
7. From the Claim Names drop-down, select the field that claims your identifier.
8. From the Destiny Field drop-down, select the Destiny field that corresponds with the Claim Name.
9. Click Save.
   

After you generate the LTI configuration information in Destiny, refer to the instructions provided by your learning platform provider to configure Destiny as an LTI tool. Following is a list of some commonly-used learning management systems:

• Blackboard
• Canvas
• ClassLink
• Desire2Learn
• Its Learning
• Moodle
• Schoology

Single Sign-On with Google

To set up Google authentication in Destiny, you first need to configure your district’s Google for Education account. This involves creating credentials in the Google Developer Console API Manager at: https://console.developers.google.com/apis/dashboard.

Note: If you do not have a district Google for Education account, use Follett's account to authorize the connection.

To configure Google SSO in Destiny, log in as the Destiny Administrator, and complete the following steps:

Click here for instructions

1. From the District page, click Setup.
   
2. Next to the district name, click .
   
3. In the SSO Configuration section, click Configure.
   
4. On the Single Sign-On Configuration page, select New.
5. From the Strategy drop-down, select google.
6. Choose one of the following options: Use Follett or Use District.
7. In the Name field, type a name of your choice.
8. If you selected Use Follett, the Client ID and Client Secret fields are not shown (Go to Step 9). If you selected Use District, complete the following fields:
   • Consumer Key: Type the Client ID you created in the Google Developer Console API Manager.
   • Consumer Secret: Type the Client Secret you created in the Google Developer Console API Manager.
   • Domain filters: If your Destiny username claim fields do not contain a domain name, type the domain name in this field. If the claim sent to Destiny matches the Destiny username claim field, leave this field blank. For example, if the Google claim field is jennystudent@school.com and the Destiny claim field is jennystudent, you would identify the Domain filter as school.com.
9. In the Destiny field drop-down, select the Destiny field that corresponds with the username claim field.
10. Click Save.

Single Sign-On with Security Assertion Markup Language (SAML)

Many school computer networks are set up so that students and staff access technology resources with a username and password. SAML SSO enables Destiny to use that same system. Once the standard is implemented, students and teachers no longer need to remember multiple usernames and passwords to access Destiny.

Setting Up SAML SSO

Deploying SAML SSO for Destiny requires the involvement of Follett’s Implementation Services team and your district IT staff. If you are interested in setting this up for your district, contact Follett Technical Support at 888.511.5114. Your district’s IT resource should be prepared to provide information about your district identity provider.