Have just moved Automation Point servers to a new Windows domain.
Previously access to Remote Viewer was locked down to a Windows group via a domain.
After using Configuration Manager > Expert Interface > Automation > Remote Viewing to change the Domain Name to the new value in Windows Security, anyone who has access to that Domain can access Remote Viewer, regardless of whether they are on the group list.
(Automation Point 11.8 > Administrating > Viewing Remote Sessions > Remote Viewer > Enabling Automation Point for Remote Viewing)
Later tested reverting the Domain Name and still facing the same problem.
The Global Sessions Settings or Local Session Settings Remote Permissions value "Permission Level = FILE" can be used to restrict access to Windows users and groups via their access to a Windows file.
Automation Point 11.8 > Administrating > Viewing Remote Sessions > Remote Viewer > Securing the Remote Viewer
From diagnostics report file CfgSetReport.html ("ProgramData\CA\CA Automation Point\Logs\) shows expected Global Sessions Settings with "Permission Level = FILE" and "Permission File = C:\Security\AP_group.txt"
*****
Global Session Settings
Messages
Global Session Prefix = SSSSSSSS TTTTTT JJJJJJJJ RRRRA
Remote Viewing
Permission Level = FILE
Permission File = C:\Security\AP_group.txt
Primary Control Mode
Enabled = 0
Web Message Viewer Enabled = No
Automated Terminal Session Window
View Only = Yes
Session Timeout
Interval = 5
Kcmd Timeout = 5000
Restart String =
*****
However there are also 2 sessions defined SESS1 and SESS2.
They both have these values for Local Session Settings with the same Prefix as the global session above but have "Permission Level = FULL"
*****
Local Session Settings
Local Session Prefix = SSSSSSSS TTTTTT JJJJJJJJ RRA
Remote Viewing
Permission Level = FULL
Permission File =
Primary Control Mode
Enabled = 0
Web Message Viewer Enabled = No
Automated Terminal Session Window
View Only = Yes
Session Timeout
Interval = 5
Restart String =
*****
The Local Session Setting "Permission Level = FULL" is overriding the Global Session Setting "Permission Level = FILE".
Modify the sessions SESS1 and SESS2 to set their Local Sessions Settings as "Permission Level = FILE" and "Permission File = C:\Security\AP_group.txt" which resolved the problem.
NOTE:
For any sessions created before the Global Sessions Settings is changed from default "Permission Level = FULL" to "Permission Level = FILE" their Local Sessions Settings do not change i.e. they still retain "Permission Level = FULL".
Only newly created sessions after the Global Sessions Settings change will also have their Local Sessions Settings changed to "Permission Level = FILE".