Please note that at the time of this writing it requires manual set up by the user. It supports Single Sign-On when you use SIPE on UNIX/Linux systems configured for GSS-NTLMSSP, a GSSAPI mechanism plugin that implements NTLM. It supports Single Sign-On when you use SIPE on Windows configured for SSPI. For company internal Office Communicator installations this the correct choice. NT LAN Manager is an authentication protocol from the Microsoft Windows world. Microsoft Lync is the new name for Office Communicator. | - field is empty | The value from Username will be used This is usually the correct value for Kerberos and Office 365 accounts DOMAIN\account | This is usually the correct value for Windows Domain accounts | Kerberos name and realm | Enterprise principal Not all authentication schemes support this account | Authentication with empty domain This is usually not the correct choice. This setting will be ignored when Single Sign-On is selected. The name SIPE should use for authentication requests.
UNIX/Linux systems require additional software and set up, but in mixed environments it is usually possible for them to communicate with the Kerberos servers from the Windows Domain. Microsoft Windows does support Kerberos out-of-the-box as it is used for Windows Domain authentication. Kerberos is an authentication scheme that supports Single Sign-On. company COMPANY COMPANY.COM | Windows Domain names The name is case sensitive, i.e. | - | In email addresses or Kerberos realm names The name is case insensitive, i.e.
DO NOT USE unless you have been explicitly advised to do so. TCP | Use an unencrypted(!) channel to communicate with the server Only very old installations will use this.
| - Auto | This is the default which selects an encrypted channel and is usually correct SSL/TLS | Use an encrypted channel to communicate with the server This is most likely the correct value if Auto doesn't work for you. The type of connection SIPE should use to communicate with the server.
Microsoft Business Professional Online Suite (BPOS) is the predecessor of Office 365. | - Auto | This is the default which tries TLS-DSK, Kerberos and then NTLM NTLM | use NTLM Kerberos | use Kerberos (Configurable) TLS-DSK | use TLS-DSK BPOS The scheme SIPE should use to authenticate the user against the server. | - first.last | In email addresses short | Windows Domain account or Kerberos user name Authentication scheme If you don't use Pidgin then you'll need to check where in your IM client you can change the SIPE settings. This setting is optional and can usually be left empty The availability of this setting depends on the version of SIPE installed on your system This setting can be found on the Advanced tab of the account setup dialog in Pidgin This setting can be found on the Basic tab of the account setup dialog in Pidgin This section defines the terms which will be used in this article.