Several security settings will be enforced after the migration. While we do recommend using the new settings for improved security, here are the steps to restore the previous behavior:
Restoring Previous Security Behavior After Migration
1. Allow access without a certificate
Change the following settings in the OPC Client/Server configuration
(Configuration View → Connectivity → OpcUaCs → UaCsConfig.uacfg):
ClientServerConfiguration -> Security -> MessageSecurity -> SecurityPolicies -> None: Enabled
2. Enable anonymous access instead of user login
Change the following settings in the mappView configuration
(Configuration View → mappView → Config.mappviewcfg):
MappViewConfiguration -> Server Configuration -> Startup User: anonymous token
3. Enable anonymous authentication in OPC Client/Server
Change the following settings in the OPC Client/Server configuration
(Configuration View → Connectivity → OpcUaCs → UaCsConfig.uacfg):
- Click the two green blocks at the top labeled “Change Advanced Parameter Visibility”
- Enable the following:
ClientServerConfiguration -> Security -> Authentication -> Authentication Methods -> Anonymous: Enabled
ClientServerConfiguration -> Security -> Authorization -> AnonymousAccess -> User Role 1: Everyone
4. Configure the user role system for anonymous access
Change the following settings in the User Role System
(Configuration View → AccessAndSecurity → UserRoleSystem → User.user):
- Assign the role “BR_Engineer” to the user “Anonymous”
- If the user does not already exist, create it without a password
5. Whitelist a File Device for mappView access
To allow access to a File Device from a running mappView application, you must explicitly whitelist it:
- Open the mappView server configuration file
2.(Configuration View → mappView → Config.mappviewcfg)* - Click “Change Advanced Parameter Visibility” in the editor toolbar
- Enter the accessed File Device Name under:
MappViewConfiguration -> Server configuration -> File device whitelist