Single sign-on (SSO) is an integral part of modern cloud-based computing. It allows your team to easily access various software systems to use their University credentials. Happily, Gecko can also be accessed using SAML SSO.
This article will walk you through the benefits of SSO and how you can start implementing it today.
Why use SSO?
We're fast seeing single sign-on (SSO) become an industry standard requirement in Higher Education applications. It's not difficult to see why. Using SSO to manage your Gecko authentication yields some big-time benefits.
For instance, new Gecko users no longer have to set and remember a password - they log in to your account with their University email address. When a staff member leaves your institution, your IT team will deactivate their University account. With SSO enabled, this will automatically rescind the ex-staff members' access to your Gecko account, meaning your data remains secure.
In short, SSO ensures your account is safer and easier to manage.
Setting up SSO
To begin with, your IT team will need the following details to configure your Identity Provider (sometimes known as your IdP):
🔎 Information you'll need to give to your IT team
- SAML Consumer URL: (account-cognito.geckoengage.com)
- SAML Audience: (urn:amazon:cognito:sp:eu-west-1_TIMcKUTug)
- Required Parameters:
* First Name
* Last Name
Once that's done, Gecko will require the following information from your IT team to set things up:
💡 Information Gecko will need from your IT team:
- Metadata / SAML XML document
- Attribute mappings (how these are named in your institution's IdP)
- Required Domains (please confirm you have authority over the entire domain)
-Should IdP Sign-out flow be turned on/off?
Any questions? Start a live chat with our support team, or feel free to explore the rest of our Academy. Spotted an error or want to suggest a future article for the Academy? Let us know here.