Policy
The qaskx-cli serve policy command is used to serve policy files to your users
as web based files. The users can be qaskx command line users or qaskx web server
users.
Policy files are the source of settings for the command and are based on your policy.
The command help is shown below.
Usage: qaskx-cli serve policy [--server-conf=<server config>] [--port=<8080>] [--address=<0.0.0.0>][-v | --vv | --vvv | --silent] [-c=<conf file>] [--colourCLI] [--offline] [--env=<environment file>]
The qaskx-cli serve policy command is for starting the server to
handle policy requests. The policy server provides a central
repository of settings.
If the configuration file is not supplied, then it is searched for in
various locations.
For more details see the documentation at https://docs.qaskx.one/qaskx-cli/cmd/server/policy/ .
Options:
-C, --server-conf Server configuration file
-p, --port Listen on port (default 0)
-a, --address Listen on address
-v, --verbose Verbose logging
--vv Verbose logging level 3
--vvv Verbose logging level 5
--silent Silent running
--colourCLI Colour terminal and command line (env $QASKX_COLOUR_CLI)
-c, --conf Configuration file (env $QASKX_CONFIG_FILE)
--offline Offline mode (env $QASKX_OFFLINE)
--env Environment file to use (default ".env")
Details
The policy server is a read only server to supply policy files.
There are protection mechanisms to ensure only authorised files are supplied to consumers.
To ensure policy files are not tampered, they are signed and the qask-cli command is hard coded with certificates and signatures. To use the policy other than a simple proxy will require the organisation to contact the qaskx-cli authors.
IMPORTANT: You cannot be the default serve for your own policy configurations, with out having the policy files signed. Policy signatures for redirection to your server has to be in place first for security reasons.