[
https://issues.apache.org/jira/browse/TC-187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16130653#comment-16130653
]
ASF GitHub Bot commented on TC-187:
-----------------------------------
Github user rawlinp commented on a diff in the pull request:
https://github.com/apache/incubator-trafficcontrol/pull/360#discussion_r133741257
--- Diff: traffic_ops/app/lib/UI/SslKeys.pm ---
@@ -34,7 +34,7 @@ sub add {
&stash_role($self);
#get key data from keystore
- my $response_container = $self->riak_get( 'ssl', "$xml_id-latest");
+ my $response_container = $self->riak_get( 'ssl', "ds_$ds_id-latest");
--- End diff --
a preexisting key won't be found and won't get stashed. I'm not sure how
much of an issue that might be.
> Update delivery service makes SSL keys invalid
> ----------------------------------------------
>
> Key: TC-187
> URL: https://issues.apache.org/jira/browse/TC-187
> Project: Traffic Control
> Issue Type: Bug
> Components: Traffic Ops
> Reporter: Zhilin Huang
> Assignee: Zhilin Huang
> Labels: ssl, xml-id
>
> Modify xml-id or subdomain in a https delivery service will make existing SSL
> keys invalid.
> And there is problem to generate keys if using "http and https" together with
> 1 host_regex, and 1 path_regex.
> BTW, the certificate returned by RESTful API is not consistent with that GUI.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
