mitchell852 opened a new issue #5075:
URL: https://github.com/apache/trafficcontrol/issues/5075
## I'm submitting a ...
- bug report
## Traffic Control components affected ...
<!-- delete all those that don't apply -->
- Traffic Ops
- Traffic Ops ORT
- Traffic Portal
- Traffic Router
- Traffic Vault
## Current behavior:
a ds w/ ssl keys has ssl keys of 1 of 3 types:
- self-signed ssl keys generated via the TO API generate endpoint
- ssl keys generated via the Lets Encrypt TO API generate endpoint
- ssl keys that were manually uploaded (that were signed/generated via a 3rd
party)
when switching the cdn of a ds, 2 things must happen:
1. the ssl keys need to be moved from cdn1 to cdn2 (this is done with #4988 )
2. the ssl keys need to be potentially regenerated / uploaded to account for
the modified DS fqdn due to the cdn change.
## Expected behavior:
Up for debate.
## Minimal reproduction of the problem with instructions:
- Create a DS in cdn1 and set protocol to `http and https`. Generate
self-signed ssl keys. Queue updates and snapshot. Test the DS.
- Change the DS cdn to cdn2. Snap and queue updates. Test the DS.
<!--
Licensed to the Apache Software Foundation (ASF) under one
or more contributor license agreements. See the NOTICE file
distributed with this work for additional information
regarding copyright ownership. The ASF licenses this file
to you under the Apache License, Version 2.0 (the
"License"); you may not use this file except in compliance
with the License. You may obtain a copy of the License at
https://apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing,
software distributed under the License is distributed on an
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
KIND, either express or implied. See the License for the
specific language governing permissions and limitations
under the License.
-->
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
