176 - ID Please
Hi there, eMagiz developers! We have changed our login procedure to increase the security of the data stored within the portal. As of this moment, you must provide your MFA code upon login. On top of that, we have updated the look and feel across the portal. Furthermore, we will introduce functionality that allows you to validate system messages containing multiple namespaces with the standard eMagiz tooling. Some fixes surrounding the graphs in managing our next-generation runtime (Gen3) are among the feedback items. 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. 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.
After logging in with your username and password, you will be prompted with a second screen into which you need to fill in your MFA code. Once you have done so successfully, you may enter our 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.
Improved Styling
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.
Multiple Namespace Validation
Building on an earlier release in which we introduced the functionality to add multiple namespaces to a system message, we now present the option to validate the system message with multiple namespaces. With this functionality, it is now easy to use the standard eMagiz transformation even when sending data from or to a system message that uses multiple namespaces.
Feedback items
Apart from the key updates around functionality, we have also solved other feedback items.
Improved Manage Graphs Generation 3 runtimes
With this release, we have made several improvements to what is shown in the runtime statistics for a generation 3 runtime, so they reflect the more accurate values and are better interpretable by a user without knowing the technical details.
Fancy Forum Answers
As always, a gentle reminder to all to ask questions via the Q&A forum. The Q&A forum is available in the eMagiz iPaaS portal, so we can all benefit from the knowledge within the community. For some inspiration, take a look at these forum answers:
- Constant read timeout on REST call
- Synchronous exits in eMagiz Mendix connector not working in Mendix 9.x
- lang.OutOfMemoryError: Metaspace
Key takeaways
Thanks to all that help build, those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you:
- If you have questions surrounding our Program Increment Planning, please get in touch with
- If you have feedback or ideas for us, talk to the Platypus
- Please inform us of new additions to the store (productmanagement@emagiz.com) so we can all benefit from these.
- Clear your browser cache (Ctrl + Shift + Del)
- Check out the release notes here
- Start thinking about how the license tracker can aid your development
- Start thinking about major, minor, and patch
- Upgrade to the latest build number
- Keep making great integrations
Let's stay in touch and till next time!