top of page
Configuring Single Sign On (SSO)
TIMELINE: THIS SHOULD BE COMPLETED 3-4 WEEKS PRIOR TO YOUR LAUNCH DATE.
Action items: After reading this page, here are the action items that need to be completed:
Review the SSO requirements
Complete and submit the SSO form with a metadata file
Work with a Topanga.io engineer to complete testing / setup (if needed)
SSO (single sign on) is a signup method offered to campuses launching ReusePass to streamline the authentication of their users.
Upon signup, students will be redirected to sign into their university account. Then, the attributes that the campus requests for user identification will be sent to ReusePass and associated with the student’s account.
To begin the SSO implementation process we require our REUSEPASS SSO IMPLEMENTATION FORM to be completed. Once submitted, a member of our engineering team will reach out if anything else is needed to complete setup.
🗓️ Scheduling Considerations: Topanga requires at least two weeks lead time for SSO integrations to be completed, subject to lead engineer’s availability.
Requirements for SSO setup, requested on above linked form:
Identifying if your system supports the SAML protocol. If your campus does not use SAML protocol, notify our team immediately.
The fields you would like us to capture
Phone Number and Campus Email are both required
Campus ID (student ID #) and Student Name are optional, but highly recommended for ease of charging and customer service support
A set of credentials used to test the SSO integration
Test account name
Test account password
Test account campus ID
A metadata file from your campus
For SSO FAQ’s and all relevant IT policies including SOC2 and HECVAT please visit THIS PAGE (password = wasteless) or download below:
Questions? Email techsupport@topanga.io
bottom of page