🛡️ A private certificate authority (X.509 & SSH) & ACME server for secure automated certificate management, so you can use TLS everywhere & SSO for SSH.
step-ca fails to start with error parsing https://keycloak-server/auth/realms/gfpd/.well-known/openid-configuration: issuer cannot be empty
Your Environment
OS - Docker container
step-ca Version - 0.25.2
Expected Behavior
I'd like to be able to start step-ca so that I can remove or repair the faulty provisioner config
Actual Behavior
step-ca errors on start, no way to change the provisioner config
Additional Context
I attempted to remediate by turning off remoteAdmin which allows step-ca to start, but it also appears to not read the database, so the provisioner list is [] when remoteAdmin is false, leaving me no ability to delete or edit the faulty provisioner.
Contributing
Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).
Steps to Reproduce
error parsing https://keycloak-server/auth/realms/gfpd/.well-known/openid-configuration: issuer cannot be emptyYour Environment
step-caVersion - 0.25.2Expected Behavior
I'd like to be able to start step-ca so that I can remove or repair the faulty provisioner config
Actual Behavior
step-ca errors on start, no way to change the provisioner config
Additional Context
I attempted to remediate by turning off remoteAdmin which allows step-ca to start, but it also appears to not read the database, so the provisioner list is
[]when remoteAdmin is false, leaving me no ability to delete or edit the faulty provisioner.Contributing
Vote on this issue by adding a 👍 reaction. To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).