Skip to content

[Feature request]: Change defaults for CA_HOSTNAME and CERTNAME #58

@defnull

Description

@defnull

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 list fails because it tries to connect to https://puppet:8140.
  • The CA certificate still lists DNS:puppet in addition to DNS: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_HOSTNAME should default to hostname -f
  • CA_HOSTNAME should default to OPENVOXSERVER_HOSTNAME.
  • CERTNAME should also default to OPENVOXSERVER_HOSTNAME.
  • The server CA certificate should not contain puppet as an additional alt name unless this is explicitly requested by DNS_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

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    Status

    No status

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions