Registration¶
Initial registration¶
To register the proxy, you will need to provide Ubuntu SSO credentials for the desired account you wish to link the proxy with, and answer some simple questions about your deployment:
sudo enterprise-store register --https
or:
sudo enterprise-store register
If the --https option is omitted, the resulting assertion
instructing client devices to use the proxy instead of the upstream store will
instruct them to use HTTP to connect to the proxy instead of HTTPS.
You can examine your proxy’s registration status with:
enterprise-store status
This will show the registration status of your proxy, as well as local status information of this store’s host.
Example:
$ enterprise-store status
Store URL: http://proxy.example.com
Store DB: ok
Store is in air-gapped mode
Store ID: id
Internal Service Status:
memcached: running
nginx: not running: 500 Server Error: Internal Server Error for url: http://127.0.0.1/_status/check
packagereview: running
packagereview-worker: running
publishergw: running
snapassert: running
snapauth: running
snapdevicegw: running
snapdevicegw-local: running
snapident: running
snapmodels: running
snapproxy: running
snaprevs: running
snapstorage: running
storeadmingw: running
At this point, your proxy will be assigned a Store ID, which can be retrieved with the status command. This will be used in later commands and to identify your proxy for support purposes.
After successful registration it’s advised to securely store the private key generated during the process. This key is your proxy’s identity. The key pair can be viewed using:
sudo enterprise-store config proxy.key.public proxy.key.private
Next step¶
Configure the proxy to serve HTTPS traffic if --https
registration option was used, or proceed to configure client
devices.