Skip to content
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.

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

Portal -- SSL certificates for HTTP* deliveryservices should be created as wildcards #1465

Closed
dneuman64 opened this issue Oct 25, 2017 · 2 comments · Fixed by #1594
Closed
Assignees
Labels
bug something isn't working as intended high impact impacts the basic function, deployment, or operation of a CDN Traffic Portal v1 related to Traffic Portal version 1
Milestone

Comments

@dneuman64
Copy link
Contributor

When generating SSL certificates for a HTTP deliveryservice via Traffic Portal, the common name includes the routing name. The common name should be a wildcard since the certs will potentially be on hundreds of servers.

@dneuman64 dneuman64 added bug something isn't working as intended high impact impacts the basic function, deployment, or operation of a CDN Traffic Portal v1 related to Traffic Portal version 1 labels Oct 25, 2017
@mitchell852
Copy link
Member

maybe @DylanVolz can look at this one as he added the SSL cert functionality to TP and may be most familiar with the code.

@dneuman64
Copy link
Contributor Author

I also noticed that TP will change the hostname to be incorrect if you paste certificates in for a HTTP DS. This needs to be fixed before 2.2 is released

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug something isn't working as intended high impact impacts the basic function, deployment, or operation of a CDN Traffic Portal v1 related to Traffic Portal version 1
Projects
None yet
2 participants