Skip to content

Add proxy domain as CA DNS name requirement to proxy production considerations #414

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
hslatman merged 1 commit into from
Jun 18, 2025
Merged

Add proxy domain as CA DNS name requirement to proxy production considerations #414

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions step-ca/certificate-authority-server-production.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -554,6 +554,12 @@ There's a few things you should know before you deploy this setup:
(or set `STEP_MTLS` to `false`).
This will trigger an alternative renewal flow that employs authentication tokens.
(See `step ca renew --help` for more details.)
- The authentication token is a JWT that contains the CA URL in its audience claim.
The CA expects the audience to match one of its configured DNS names.
If your proxy server is available on a different domain than your CA,
your CA needs to be configured to have the domain of your proxy server
as one of its DNS names in the `dnsNames` property in `ca.json`.
(See [configuration options](./configuration.mdx#basic-configuration-options) for more details.)
- By design, `step-ca` does not have an option to run in HTTP only.
Philosophically, we value perimeterless security
and we believe people should use encryption everywhere.
Expand Down