Search: "mfa"

Configure MFA - User Account

crashcourse-platform-security-add-mfa

Note that the MFA is valid for eight hours except for logging out.

[[image:Main.Images.Microlearning.WebHome@crashcourse-platform-security-add-mfa--add-mfa-userlevel-mfa-screen-before-config.png]] - Download the Google authenticator app on your device - Press the green button called "Configure MFA" - Scan the QR code from the Google authenticator app on your device [[image:Main.Images.Microlearning.WebHome@crashcourse-platform-security-add-mfa--add-mfa-userlevel-scan-qr-code.png]] - Once done, select the green button to indicate the setup is done Note that you should contact your partner manager if you encounter problems while setting up your MFA. == 4. Key takeaways == MFA can help you: * Secure data * Better verify who is logging in To set up MFA, you need: * Google Authenticator App * QR Code under the MFA section within the Administration section in the portal == 5.

Release that brings a change in the MFA authentication across the portal. In addition, this release includes several other improvements and tackles some minor issues.

Find out more on our Release blog. Major Changes MFA authentication: A new step has been introduced where the MFA code is required every time when logging in the portal. This means that all information in the portal is secured behind the MFA check instead of only the most sensitive data as it currently stands.

Release that brings a change in the MFA authentication across the portal. In addition, this release includes several other improvements and tackles some minor issues.

Find out more on our [[Release blog>>Main.Release Information.Release Blogs.176 - ID Please.WebHome||target="blank"]]. ==== Major Changes ==== * MFA authentication: A new step has been introduced where the MFA code is required every time when logging in the portal. ** This means that all information in the portal is secured behind the MFA check instead of only the most sensitive data as it currently stands. * Portal - UI: With this release, we have improved the general look and feel of the platform. ** With the improved look and feel, we have created a more uniform user interface across the various phases of the eMagiz platform. ** We have made it much more apparent when you select an input field which input field you are currently filling in.

. (#642) Bug fixes Login - MFA: Fix for enter key was not working on MFA screen to verify your MFA code after entering the code incorrectly first time. (#651) Homepage: Improved performance of loading the questions which contain high quality images. (#496) Design - Architecture: Topic storages' configured size can not be increased more than what you are contractually allowed to use. (#635) Create - Flow Designer After un-transferring integrations that share a combined entry flow, all of their auto-generated components are removed from the entry connector. (#488) Performance is improved significantly We fix an issue that you cannot start or stop the flow designer when you have been opened the transformation screen.

. (#642) ==== Bug fixes ==== * Login - MFA: Fix for enter key was not working on MFA screen to verify your MFA code after entering the code incorrectly first time. (#651) * Homepage: Improved performance of loading the questions which contain high quality images. (#496) * Design - Architecture: Topic storages' configured size can not be increased more than what you are contractually allowed to use. (#635) * Create - Flow Designer ** After un-transferring integrations that share a combined entry flow, all of their auto-generated components are removed from the entry connector. (#488) ** Performance is improved significantly ** We fix an issue that you cannot start or stop the flow designer when you have been opened the transformation screen. * Create - Transformation: refresh button has been reintroduced * Deploy - Architecture: The machines have been sorted by their configurated order. (#468) ==== Remarks ==== * Mendix Runtime has been upgraded to Mendix 9.12.2.

Furthermore, we have some improvements on the MFA configuration. In addition, this release includes several other improvements, and tackles some minor issues.

Portal: After logging in, users who have not configured MFA will be prompted with the page for setting up the Google Authenticator.

Portal: Improved the auto-generation of technical names by only removing the vowels if the length limit requires it. (#339) MFA: You can type in your MFA code and press enter key to validate your code. (#132) License tracker: On-premises and Data sink (Cloud) information removed. (#611) Capture - Consumer API integration: Improved name validation when adding a new consumer API integration.

Furthermore, we have some improvements on the MFA configuration. In addition, this release includes several other improvements, and tackles some minor issues.

For specific information please check out this link to the [[release notes>>https://docs.emagiz.com/bin/view/Main/Release%20Information/Runtime/eMagiz%20Mendix%20Connector%20-%205.1.0||target="blank"]] ==== Major Changes ==== * The UI has gotten several improvements for usability. * Portal: After logging in, users who have not configured MFA will be prompted with the page for setting up the Google Authenticator.

It helps you to refresh a view and update the errors in the meantime. (#589) * Manage - Monitoring: Gen3 monitoring pages merged with the Gen2 monitoring pages. * Portal: Improved the auto-generation of technical names by only removing the vowels if the length limit requires it. (#339) * MFA: You can type in your MFA code and press enter key to validate your code. (#132) * License tracker: On-premises and Data sink (Cloud) information removed. (#611) * Capture - Consumer API integration: Improved name validation when adding a new consumer API integration. * Design - API management: Finding resources in the Catalog API is easier from now on.

So let us dive into all that we have to offer this time around! == **MFA Upon Login** == We have tightened up our security policies with this release by requiring an MFA check when logging in to the portal.

If you cannot provide the correct code or have lost the MFA code, please press the Lost MFA code link to see which steps to take to set up the MFA code generator on your device again. Note that when you log in for the first time (without having MFA configured), you will be asked to configure MFA on your device first before you can log in.

So let us dive into all that we have to offer this time around! == **MFA Configuration** == After you log in and you do not have configured your MFA yet you will be prompted by the system to set up the MFA configuration. Note that users that don’t configure the MFA will not be allowed to access anything within the portal until they have configured the MFA. == **Feedback items ** == Apart from the key updates around functionality, we have also solved other feedback items.

//__Entering your MFA__// Whit this release we have improved the process of entering your MFA. At first we have ensured that when you click on the field to enter your MFA the cursor will always start at the front.

In the administration section of the user, an MFA token can be used to enable the Multifactor Authentication on a user level.

The model owner manages the user permissions and needs to have the MFA authentication level activated before making any changes

Suggested Additional Readings == * [[Fundamental (Navigation)>>doc:Main.eMagiz Academy.Fundamentals.WebHome||target="blank"]] ** [[eMagiz Security Guide (Explanation)>>doc:Main.eMagiz Academy.Fundamentals.fundamental-emagiz-security-guide||target="blank"]] * [[Crash Courses (Menu)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.WebHome||target="blank"]] ** [[Crash Course Platform (Navigation)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.WebHome||target="blank"]] *** [[Configure MFA - User Account>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-security-add-mfa.WebHome||target="blank"]] )))((({{toc/}}))){{/container}}{{/container}}

Prerequisites == * Completed all previous exercises of the Crash course Platform * Completed all previous microlearnings of the Crash course Platform * Access to my.emagiz.com with your own account and MFA configured * A model in which you can create this exercise == 2.

//__Block adding the same port twice in the eMagiz Cloud route__// As of now, you will be able to press Enter even when you forgot to enter an MFA code the first time or filled in an incorrect MFA code, for example. Furthermore, we have slightly improved the look and feel of the login through MFA. //__Removing all-entry components__// Before, it could happen that specific components remained in an all-entry once you removed an onramp.

In the administration section of the user, upon first login an MFA configuration needs to be executed by the user so they can access models to which they have been granted rights.

For more information, check out this [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-security-add-mfa.WebHome||target="blank"]]. An MFA response is required for model owners to manage the permissions on a model level.

In addition, the model owner manages the user permissions and needs to have the MFA authentication level passed before making any changes (which is asked of the model owner upon login)