Share via


Authentication

Authentication allows the RTC client to verify that messages from other clients and servers are not impersonated. The version 1.0 RTC Client API supports Basic and Digest authentication. The RTC Client version 1.2 API supports NTLM and Kerberos authentication. The following topics contain information on the available authentication methods.

Note  It is possible for someone to intercept information by replacing the SIP server, which would result in forwarding SIP requests to erroneous servers. The application should therefore ensure that a means to authenticate the server is enabled. For the application to authenticate the server, the TLS transport type must be specified in the profile.