Skip to content
This repository has been archived by the owner on Sep 2, 2021. It is now read-only.

Variable certificate names #18

Open
emcniece opened this issue Mar 8, 2017 · 1 comment
Open

Variable certificate names #18

emcniece opened this issue Mar 8, 2017 · 1 comment

Comments

@emcniece
Copy link
Member

emcniece commented Mar 8, 2017

Some users are migrating existing certificates in to RP, and these certs may not be named in the way that we expect (fullchain, privkey). Also, some containers may actually use these certificates internally and expect them to be named in certain ways.

RP should have labels to specify custom certificate names.

@Munsio
Copy link
Member

Munsio commented Mar 9, 2017

When you use other names than acmetool provides RP is not able to renew those certificates. I don't know if this is something we really want?

Also imho - RP is an SSL-Termination Proxy so if an container itself needs an functional ssl-cert it would be better to proxy the ssl-request to it and this can be achieved with the vhost.d config files or am i wrong?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants