Just created a small login system using the ‘MpUserXLogin’ FB, when a successful login on this FB is completed the elements properties such as ‘PermissionView’ was not effected.
When I checked the ‘::SYSTEM:clientInfo.userId’ it was also unchanged so they are clearly not linked?
Any suggestions on which way is best for User Management and why these would be used separately?
Thanks,
Elliott
The concept of mappView is that the mappView visualization can be loaded in chrome browser on multiple devices or in multiple chrome browsers. The login widget logs in locally on the device not in the PLC. Since mappView 5.18 or so mappView can work with MpUserX settings and definitions, but still the login widget logs in locally and not in the PLC.
If you have only one device which shows the visualization, you could try to synchronize the PLC MpUserX login with mappView login widget or vice versa. This could be beneficial when also using mappAudit. You should use HTTPS communication in this case, otherwise passwords could be sent in clear text.
I’m marking Corne’s reply as the solution because I think it answers your questions well. If you have any additional related questions, feel free to reply!