Web Services¶
On a web proxy node only, Self-service and admin Web services can be disabled, re-enabled and listed if required. The task should be carried out after provisioning and if the admin or Self-Service GUI for example needs to be disabled for security purposes.
Note
It is strongly recommended not to allow customer end-users the same level of administrator access as the restricted groups of provider- and customer administrators. This is why Self-service web proxies as well as Administrator web proxies should be used.
Systems with Self-service only web proxies are only recommended where the system is customer facing, but where the customer does not administer the system themselves.
The commands should be run on the relevant web proxy node. It is not recommended that the commands be run on a standalone system, but only on a cluster.
In particular, the commands to disable or enable web services will automatically reconfigure and restart the nginx process, so some downtime will result. Request URLs to a disabled service will redirect the user to the active service.
To disable admin or self-service web services on a web proxy node, run the command on the relevant node:
web service disable <selfservice|admin>
To enable admin or self-service web services on a web proxy node, run the command on the relevant node:
web service enable <selfservice|admin>
To list disabled web services on an admin or self-service web services web proxy node:
web service list
For example:
platform@cscluster1:~$ web service list disable: admin
