RTC Authentication
Other versions of this page are also available for the following:
.gif "A hyphen indicates that the information in this topic is not relevant for this platform, or that the platform does not support the API that is listed.")
.gif "A checkmark indicates that the information in this topic is relevant for this platform, and that any API listed is also supported on this platform.")
8/28/2008
Client applications use authentication to verify that messages from other clients and servers are not impersonated.
RTC version 1.2 supports the following authentication methods:
- Basic, discussed in Basic Authentication and RTC
- Digest, discussed in Digest Authentication and RTC
- NTLM, discussed in NTLM Authentication and RTC
- Kerberos, discussed in Kerberos Authentication and RTC
In terms of security, the RTC API prioritizes the authentication schemes as follows, in order from most secure to least secure:
- Kerberos
- NTLM
- Digest
- Basic
Note
Someone can intercept information by replacing a SIP server and forwarding SIP requests to other servers. Client applications should ensure that the server is authenticated. To authenticate the server, the Transport Layer Security (TLS) transport type must be specified in the connection profile.
For more information about setting security parameters, see the Security information at this Microsoft Web site.