-
Notifications
You must be signed in to change notification settings - Fork 19
Description
Use Case
I started a new openvoxserver container with the custom hostname openvox as well as OPENVOXSERVER_HOSTNAME=openvox and assumed this is enough, but it is not:
- Calling
puppetserver ca listfails because it tries to connect tohttps://puppet:8140. - The CA certificate still lists
DNS:puppetin addition toDNS:openvox.
The first issue is caused by CA_HOSTNAME defaulting to puppet instead of OPENVOXSERVER_HOSTNAME or hostname -f, which I find unintuitive. Setting CA_HOSTNAME=openvox solves this issue.
The second issue persists, even if I set CERTNAME=openvox. The puppet alt name seems to be hard coded somewhere?
Describe the solution you would like
A container with minimal configuration should use OPENVOXSERVER_HOSTNAME and fall back to hostname -f for all aspects that need to know the servers hostname. It should not assume that the hostname is puppet.
OPENVOXSERVER_HOSTNAMEshould default tohostname -fCA_HOSTNAMEshould default toOPENVOXSERVER_HOSTNAME.CERTNAMEshould also default toOPENVOXSERVER_HOSTNAME.- The server CA certificate should not contain
puppetas an additional alt name unless this is explicitly requested byDNS_ALT_NAMES.
Describe alternatives you've considered
Documenting more prominently which config values are absolutely required if the hostname differs from puppet.
Additional context
No response
Metadata
Metadata
Assignees
Labels
Type
Projects
Status