All Collections
Feature Releases
2023
Release Notes
Enhanced Login Security | December 2023
Enhanced Login Security | December 2023
Michael Stephenson avatar
Written by Michael Stephenson
Updated over a week ago

Enhanced login security options

⚠️ Element451 Admins: You may need to update your login preferences after release. See Action Items below.

This release will occur between 7-9pm EST on December 6. We don't anticipate any downtime or other impacts on our service.

Overview

This update enables customizable sign-on and authentication options, including SAML2 Single Sign On, Element451, and Google, with optional 2FA for the Element451 local login. Institutions can select permitted login methods to meet their needs and preferences.

You can find these new settings by clicking on your profile picture in the top right corner and then navigating to Settings > Manage Users > Security.

Details

  • Ability to select which login methods are permitted for your instance:

    • Local Element451 Login (username & password)

    • SAML2 Single-Sign-On

    • Google Login

  • Optional 2-factor authentication is available when using Element451 local login (code is emailed to the user)

  • All login options are now available for both staff and student login

  • Removed Facebook and Twitter Login options from student-facing portals, including Applications and Microsites.

System Defaults

Upon release, the following defaults will be in effect. This could enable additional options beyond your current configuration.

  • Internal (Staff) Authentication Settings for Access to Element451

    • Password

    • Single Sign-on (SSO)

    • Google

    • API Key

  • External (Student) Authentication Settings for access to applications and microsites

    • Password

    • Google

Action Items

We've designed this release to be backward compatible for most of our partners. However, our system defaults may enable options you don't wish to offer. Element451 admins are encouraged to review their enabled options.

Disabling Username/Password Method + Using API

If you've built your own API integration, disabling password login to enforce SSO, will break your integration. Be sure to create an API key for authenticating your API calls.
​
API integrations managed by Element451 will not be effected if you turn off password log in options.

Did this answer your question?