Using HTTP(s) over the SUPMessagingChannel

(Optional) Clients can securely communicate with the backend via the server through the HTTPS transport protocol. By using SSL over the SUPMessagingChannel, all messages are encrypted and authenticated to ensure secure communication.

• Enabling HTTP(s) as a Transport Protocol
  You can set HTTPs as the transport protocol that the OData client should use to communicate with any host (Example: Relay server).
• Enabling a Listener for HTTPS Support with Server Certificate Validation
  When a client attempts to connect to a host (like a relay server), this connection is authenticated with a basic authentication challenge.To verify if the server certificate is trusted or not, the application registers a listener object with the OData SDK. If the server certificate is trusted, the connection is successful. If the server certificate is not trusted, it is rejected and the connection fails.
• Enabling a Listener for HTTP(s) Support with Basic AuthChallenge
  When a client attempts to connect to a host (like a relay server), this connection is authenticated with a basic authentication challenge.To setup a basic authentication, the application registers a listener with OData SDK. If the IODPHTTPAuthChallengeListener is not registered, an HTTP_AUTH_FAILURE error is returned when a challenge is received.
• Registering a Listener for HTTP Error in Android Applications
  To ensure that OData Android clients are notified of HTTP errors while establishing a connection with the network edge, implement a listener.