Configuring Single Sign On
If your organization uses an existing login portal or intranet for your community, Localist can be setup to accept that same information when logging in to keep things simple and organized.
Localist works with LDAP and Shibboleth/SAML2/Azure AD.
If using a different Custom Domain for onboarding vs. live platform, you can still get started setting up Single Sign On. Once you've added your live Custom Domain, your configuration will need to be updated on Localist's end and you'll need to refresh our metadata in your system.
To get started, complete the survey below for your chosen SSO integration. Don't see yours listed? Contact your Client Success Manager via email@example.com!
Integrating with LDAP
- It is not possible to use LDAP + Localist account logins.
- With LDAP, users will select the Login link on the calendar homepage and sign in directly in the login modal. If other login options are available then they will be listed below (see Login with Facebook below).
Integrating with SAML2 / Azure AD
SAML 2/Azure AD is set up with a metadata swap, which requires our development team to work directly with campus IT to configure the technical information. Each user will login from a campus-hosted SAML 2/Azure AD/Shibboleth page and will be passed through to the Localist system upon successful authentication.
- If the Localist and/or Facebook login methods are allowed, then theSAML 2/Shibboleth login will appear as a button below the username/password fields for Localist accounts.
- If Shibboleth/SAML 2/Azure AD is the only method allowed, then the login modal will not be displayed. Instead, the login link will be linked with directly with your Shibboleth/SAML 2/Azure AD login page. The separate sign up functionality that is tied to the Localist login method will also disappear.