{"id":28406,"date":"2024-03-19T11:42:56","date_gmt":"2024-03-19T08:42:56","guid":{"rendered":"https:\/\/trueconf.com/blog\/?p=28406"},"modified":"2024-10-04T19:50:51","modified_gmt":"2024-10-04T16:50:51","slug":"configuration-of-kerberos-sso-in-trueconf-server","status":"publish","type":"post","link":"https:\/\/trueconf.com/blog\/knowledge-base\/configuration-of-kerberos-sso-in-trueconf-server","title":{"rendered":"Configuration of Kerberos SSO in TrueConf Server"},"content":{"rendered":"
TrueConf Server supports password-free authentication with the help of single sign-on technology and the Kerberos protocol. This feature will be available if the integration with a directory service is configured via LDAP<\/a>. Read this article<\/a> to take a look at some examples.<\/p>\n <\/p>\n The overall guideline for setting up Kerberos SSO includes the following steps:<\/p>\n In the context of Kerberos SSO, it is important to understand the meaning of Service Principal Name (SPN)<\/b>. What is it? SPN<\/b> is the unique identifier of a service instance. In our case TrueConf Server acts as such a service for the domain controller. SPN consists of several parts:<\/p>\n\n
protocol\/server.name@DOMAIN<\/pre>\n