Bug #24677
closed
mgr/dashboard: RGW proxy can't handle self-signed SSL certificates
Added by Volker Theile almost 6 years ago.
Updated about 3 years ago.
Description
It's not possible to communicate with a RGW Admin Ops API running on 443 and using a self-signed certificate.
- Subject changed from RGW proxy can't handle self-signed certificates to mgr/dashboard: RGW proxy can't handle self-signed certificates
- Subject changed from mgr/dashboard: RGW proxy can't handle self-signed certificates to mgr/dashboard: RGW proxy can't handle self-signed SSL certificates
- Backport set to mimic
- Affected Versions v13.2.0 added
- Affected Versions deleted (
v13.2.1, v14.0.0)
- Affected Versions v13.2.1, v14.0.0 added
- Affected Versions deleted (
v13.2.0)
- Affected Versions v13.0.0 added
- Affected Versions deleted (
v13.2.1, v14.0.0)
- Affected Versions v13.2.0 added
- Affected Versions deleted (
v13.0.0)
- Status changed from New to Resolved
- Pull request ID set to 22735
- Status changed from Resolved to Pending Backport
- Copied to Backport #39317: mimic: mgr/dashboard: RGW proxy can't handle self-signed SSL certificates added
- Status changed from Pending Backport to Resolved
While running with --resolve-parent, the script "backport-create-issue" noticed that all backports of this issue are in status "Resolved" or "Rejected".
- Project changed from mgr to Dashboard
- Category changed from 132 to General
Also available in: Atom
PDF