I posted on the Tiger VNC forum and someone suggested that this may be a result of PolicyKit (now called PolKit, I believe). Does anyone know how to change this policy?
These are all machines behind a firewall in a small startup. It would be much easier if I could get GUI admin rights when I use VNC to connect to the server.
I've installed (Tiger) VNC Server on a new Centos 7 install.
It seems to be working ok but when I use VNC to connect as user admin (created as ua system administrator) it does not get administrator rights.
For example, via VNC the admin user cannot change network settings but when logged in directly the same user can change network settings. Same for other administrator functions.
I suspect its something to do with the PAM security context or the
runuser -l command that starts the server but I can't seem to find out what to change.
Any suggestions most appreciated.
I setup the VNC Server these instructions from this blog post.
and from the directions at the top of the file:
man systemctl page