I don't think there is a way around that. the RGW code does not allow
user/password on non-ssl transport.
what is the issue with SSL between the balancer and the RGW?
if you have issues with self-signed certificates, maybe there is a way on
the balancer to not verify them?
On Wed, Apr 28, 2021 at
Hi,
What we have found seems like it is a blocking issue when I terminate https on
a loadbalancer and between the loadbalancer and rgw http is the mode. So seems
liket he ssl termination has to be done on the rgw and can't be done on the
loadbalancer? Or how we can workaround it any idea?
Here
