The user created through the OperatorManager(In Operator Site) has normal DC permissions and application permissions, but when viewing the Alarm Report on the web interface, they cannot log in and always receive an error message indicating an incorrect account password.
What could be the possible cause of this problem?
You have to create your operators in the engineering environment, perform a build and a download.
Creating a user in the operator environment only applies to this environment and therefore to the applications in this environment.
However, since web queries do not happen locally but always via cluster and/or runtime, this cannot work in this case.
Best regards
Understood, thank you
So for end users, the relevant personnel are rotating positions, and there will be different personnel changes every year. At this time, it is necessary to create corresponding report management functional personnel (usually equipment maintenance management personnel), and describe the alarms in the alarm report;
Do you have any good suggestions for this business scenario?
Patching or expanding the relevant database from the application side is not permitted (for security and validation reasons) and is also not intended.
Furthermore, it would be highly complex as passwords must be subject to a HASH algorithm and encryption.
I suggest that you create a global login which is only used for working with the reports. All other rights can then be revoked.
This means that the new operator in the operator environment receives a login for operating the DisplayCenter etc. and then works with the global “WebLogin” when logging in to the reports.
I hope this is sufficiently understandable.
I found one more possibility:
AprolUpdateAccessDB --help
Purpose: Mirroring all operators (incl. locally added operators) from local runtimedb to all project-related databases within the runtime environment. By default only the databases on the local server are modified.
Usage: AprolUpdateAccessDB [options]
-a, --allNetworkServers transfer operators to systems on ALL hosts
–ver print short version and exit
-v, --version print version and exit
-h, --help print this help and exit
You may try this as well. Maybe in future Releases this is not any longer supported.