Email Based Multi-Factor Authentication
Previously, SMS (text message) and authenticator apps were supported factors for lms managed multi-factor authentication. We have extended this feature to include email as a factor that can be configured by a user.
With the email based multi-factor authentication, a one-time code is emailed to the user during the login process, and they are required to provide the supplied code to complete the login process. We recommend not enabling this factor if your users use/have access to shared email accounts.
As is the case for all supported factors, this applies only to lms managed accounts, and does not apply to users who use single sign-on to access the lms.
Learner Portal Multi-Factor Authentication
Previously, multi-factor authentication could be applied to administrators, when they logged into the administration portal using an lms managed account. We have now extended this to support multi-factor authentication for users logging in to the web based learner portals.
This feature is disabled by default, so there will be no immediate change to the learner experience. Global administrators can choose to enabled this feature in the administration portal.
When this feature is enabled, learners are required to configure multi-factor authentication by using a supported option. At launch of this feature, the supported multi-factor authentication options will be SMS (text message), using an authenticator app (such as Microsoft Authenticator or Google Authenticator), or email.
After setting up multi-factor authentication, each time the user subsequently logs in, they must provide a one time code to access the system in addition to their username and password. Administrators can choose to mandate multi-factor authentication, or can make multi-factor authentication optional. The configured factors for multi-factor authentications are consistent between the administration and learner portals, however administrators can choose to mandate multi-factor for the administration portal, while leaving the feature disabled, or optional for the learner portal.
Note: This feature only applies to lms managed accounts, and does not apply to users who log into the administration or learner portal by using single sign-on. Where single sign-on is used, if multi-factor authentication is required, then this must be configured in your identity provider/authentication service and cannot be managed by the lms.
Content Visibility Update
Previously, it was possible to configure whether content items appeared in the web-based learner portal, mobile apps running on a phone or mobile apps running on a tablet device. This was historically widely used where different versions of content were produced for different platforms, however responsive modern content has removed the need for this feature. We have now removed this feature.
In place of this feature is a new option Hide from Mobile Apps. The new Hide from Mobile Apps checkbox enables you to configure content which should not be displayed when learners access content within the mobile apps. This may be because the content is not suitable for mobile device consumption, or because the content is dependent on a feature not support in our mobile apps, such as premium content, or custom locking rules in a curriculum.
Bug fixes
Various bug fixes.
Comments
0 comments
Please sign in to leave a comment.