Cannot get https to work

HTTPS Output:
curl -v --header "Authorization: Bearer XXXXXXXXXXXXXXXXXXXX" https://10.252.55.55:8443/scim/users
* Trying 10.252.55.55:8443...
* Connected to 10.252.55.55 (10.252.55.55) port 8443 (#0)
* schannel: disabled automatic use of client certificate
* schannel: using IP address, SNI is not supported by OS.
* ALPN: offers http/1.1
* schannel: next InitializeSecurityContext failed: SEC_E_ILLEGAL_MESSAGE (0x80090326) - This error usually occurs when a fatal SSL/TLS alert is received (e.g. handshake failed). More detail may be available in the Windows System event log.
* Closing connection 0
* schannel: shutting down SSL/TLS connection with 10.252.55.55 port 8443
curl: (35) schannel: next InitializeSecurityContext failed: SEC_E_ILLEGAL_MESSAGE (0x80090326) - This error usually occurs when a fatal SSL/TLS alert is received (e.g. handshake failed). More detail may be available in the Windows System event log.

``````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````
HTTP Output:
curl -v --header "Authorization: Bearer XXXXXXXXXXXXXXXXXXXX" http://10.252.55.55:8443/scim/users
* Trying 10.252.55.55:8443...
* Connected to 10.252.55.55 (10.252.55.55) port 8443 (#0)

GET /scim/users HTTP/1.1
Host: 10.252.55.55:8443
User-Agent: curl/8.0.1
Accept: /
Authorization: Bearer XXXXXXXXXXXXXXXXXXXXXXXXXX

• HTTP 1.0, assume close after body < HTTP/1.0 400 Bad Request < Client sent an HTTP request to an HTTPS server.
• Closing connection 0

Hi @AbuHaneef, I'm sorry for the late response to your issue deploying the SCIM bridge.

Have you been able to resolve the issue?

This article on managing TLS on a load balancer might help you: https://github.com/1Password/scim-examples/tree/master/kubernetes#self-managed-tls