Unable to log in to Control Center UI with basic authentication configured via control-center-user secret

Hello team,

After hours of going crazy and not able to figure out, I'm posting my issues here. I'm encountering couple of issues, the first one is where I cannot log in to the Control Center UI when enabling basic authentication using a secret (control-center-user) defined in the authentication.basic.secretRef section of the ControlCenter CRD.

[replicator-cloud2cloud](https://github.com/confluentinc/confluent-kubernetes-examples/tree/master/hybrid/replicator-cloud2cloud) is what exactly I'm trying to do here. I'm able to replicate the messages and everything works well except the authentication part in Control Center. If I comment out the [section](https://github.com/confluentinc/confluent-kubernetes-examples/blob/master/hybrid/replicator-cloud2cloud/controlcenter.yaml#L13C2-L16C37), I'm able to view Control Center. I have not modified the creds txt file and it should theoretically let me login using `admin - Developer1` as mentioned in the readme too.

`replicator kubectl get secret control-center-user --namespace destination -o jsonpath='{.data.basic\.txt}' | base64 -d && echo`
`admin: Developer1,Administrators`
`admin1: Developer1,Administrators`

The second issue I'm facing is I see the warning regarding the Schema Registry. Earlier I was facing an error because I didn't mention any port (https://psrc-abcdefg.us-east-1.aws.confluent.cloud) and it was hitting on port 80 and I recalled when I was working with docker, if I changed the schema registry url to 443 port it worked (https://psrc-abcdefg.us-east-1.aws.confluent.cloud:443). I tested it for this cluster too in docker and it works with the :443 url. But it shows warning and even in the control center it says schema registry is not setup when technically I did set it up. I also override `confluent.controlcenter.connect.healthcheck.endpoint=/connectors` incase if that helps, but no luck.

`[2025-10-17 21:43:11,385] WARN [armeria-common-worker-nio-2-7] [creqId=d4b66c34, chanId=f7628a97, laddr=10.244.0.34:33650, raddr=psrc-z6mnmyr.us-east-1.aws.confluent.cloud/54.152.42.150:443][https://psrc-z6mnmyr.us-east-1.aws.confluent.cloud/#GET] Unexpected 4xx health check response: [:status=401, strict-transport-security=max-age=63072000; includeSubDomains, x-request-id=1cdec6bc-c5f3-4892-b916-933563e971d7, www-authenticate=basic realm="SchemaRegistry", content-type=application/json;charset=iso-8859-1, content-length=43] A 4xx response generally indicates a misconfiguration of the client. Did you happen to forget to configure the HealthCheckedEndpointGroup's client options? (com.linecorp.armeria.client.endpoint.healthcheck.HttpHealthChecker)`

Please let me know if someone has any clue or directions to guide me. Thanks! Much appreciated for paying attention to this!

Start with the replicator-cloud2cloud example, especially controlcenter.yaml lines 13-16, and inspect the control-center-user secret created for authentication.basic.secretRef. Compare the Control Center authentication settings with the Schema Registry URL and health-check endpoint; done means the UI accepts the documented credentials and reports Schema Registry as configured without the 401 health-check warning.

Written by the indexing model from the issue text.