User Login Issue in AS6

Hi,

I am facing issue in user login.Having different kind of issue in simulation and real hradware.

Using three FB for user log in:

MpUserXLogin();

MpUserXLoginConfig();

MpUserXLoginUI();

IN SIMULATION:

I was not able see the current user in HMI - For all the users. But i can seem the same in PLC logic.

Eventhough if log in using a authenticate user, same issue occurs. Once program uploaded getting an error in logger.Shared screen shot below:

With real Hardware same occurs some time and also like giving permission to all users in intial startup itself and all tabs the error in logger in Invalid credentails username and password.

To ensure this I checked almost all the security settings in OPC UA and tried in Mapp view configuration also.

Automation studio Version - AS6.5.1.7

Automation runtime - AR 6.5.1

Mapp view Version - 6.6.0

If you have updated the project from AS4 to AS6 you need to enter the passwords for the users again due to an updated password hashing algorithm.

User Role System: Update to password hashing algorithm

Changes have been made to the password hashing algorithm. It is therefore necessary to re-enter the password for all users configured in the “Access and security/User Role System” area.

It is no longer possible to authenticate using the old stored password from the AS 4.12 project.

Automation Help: Necessary adjustments in the Automation Studio 6 project.

Thanks. I already did the same. It eliminates the user Login error (Wrong Password). Not the log in failed error.

Has your OPCUA server started? you are focusing on some follow up errors. But before you have additional errors. Focus also on OPCUA server, did it started? you have access right set up properly?

Yes. I have check it with UA Expert. I ensured the communication.

How to find the access right setup properly?

I would personally check the configuration described here How to restore previous security behavior after migration from AS4 to AS6 . If this does not help, then analyze the complete logger and all errors and warnings there. It could be that one solved error or warning before your current one will solve it. If none of this works, get in contact with local B&R support and provide them with the project. They can check your configuration together with you, something we cannot do here at the Community.

Hi,

The issue was resolved. By updating the configuration in OPCUA ,Mapp services & Mapp View Configurations.

OPCUA Config:

Mapp service:User:

Mapp View Configuration:

image

Addtionally I worked on autolog out option in runtime by using MpcomBasicConfig:

Required FB: MpuserConfigBasic- MpcomBasicConfig (Replaced for MpuserXConfig)

Stucture Type: AutoLog - MpuserXCfgType (Replaced for MpUserXLoginConfigType)

LOGIC:

MpuserConfigBasic.Enable:=TRUE;
MpuserConfigBasic.MpLink:=ADR(UserMgmtX);
MpuserConfigBasic.Data:=ADR(AutoLog);
MpuserConfigBasic.DataType:= mpUSERX_CFG_CORE;

AutoLog.UserAccount.AutoLogoutTime:=50; (50 Secs)
IF AUTOLOGOUT_ENABLE AND MpuserConfigBasic.Enable AND NOT(Autologout_read_done) THEN
	MpuserConfigBasic.CmdRead:=TRUE;
	IF (MpuserConfigBasic.CmdRead) AND (MpuserConfigBasic.CommandDone) THEN
		Autologout_read_done:= TRUE;
		MpuserConfigBasic.CmdRead:=FALSE;
	END_IF
END_IF

IF (Autologout_read_done) AND (MpuserConfigBasic.CmdRead =FALSE) AND (MpuserConfigBasic.CurrentDataSource = mpCOM_DATA_SOURCE_CFG)  THEN
	MpuserConfigBasic.CmdWrite:=TRUE;
ELSE
	MpuserConfigBasic.CmdWrite:=FALSE;
END_IF

We have enable the .cmd read, it reads value from mapp services and shows in AutoLog. Then we have command the .cmdwrite in runtime.

1 Like