176 - ID Please

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.

To benefit from the improvements, please make sure to clear your browser cache (Ctrl+Shift+Del) before signing in the first time.

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.
• 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. On top of that, we changed the look of buttons across the platform.
• Flow designer - validation filter: It is possible now to validate messages that contain multiple namespaces using the system message designed on eMagiz.

Minor Changes

• Manage - Monitoring: The memory graphs of runtimes running on Gen3 have improved.
• Deploy - Architecture: Under certain circumstances, the HTTP route for the API gateway was generated twice, causing an invalid cloud configuration.

Bug fixes

• Deploy - Properties: Specific properties could cause the property history page to break and show error popups.
• Deploy: Architecture: Improved the mechanism for updating the last known state of machines running Gen3 runtimes.