Step 2. Configure Kerberos on Alfresco server - Alfresco Content Services - 23.4 - 23.4 - Ready - Alfresco

Step 2. Configure Kerberos on Alfresco server - Alfresco Content Services - 23.4 - 23.4 - Ready - Alfresco - external

Alfresco Content Services

Platform

Alfresco

Product

Alfresco Content Services

Release

23.4

License

As an Alfresco administrator, you need to configure Kerberos on the Alfresco server that will be running either the repository tier web application (alfresco.war) or the Share web application (share.war).

These instructions use the following naming conventions for the example server, server1.alfresco.org:

<host> is the server host name (without domain name suffix). For example, server1.
<domain> is the DNS domain. For example, alfresco.org.
<REALM> is t he DNS domain in upper case. For example, ALFRESCO.ORG.

In this example, our Windows domain controller/ Active Directory/ KDC host name is adsrv.alfresco.org. The Kerberos ini file for Linux is /etc/krb5.conf.

Set up the Kerberos ini file to point to the Windows domain controller.
The default location is %WINDIR%\krb5.ini, where %WINDIR% is the location of your Windows directory, for example, C:\Windows\krb5.ini. If the file does not already exist (for example, if the Kerberos libraries are not installed on the target server), you must copy these over or create them from scratch. See Kerberos Help for more information on the krb5.conf file.
```
 [libdefaults]
 default_realm = ALFRESCO.ORG
 default_tkt_enctypes = rc4-hmac
 default_tgs_enctypes = rc4-hmac
 [realms]
 ALFRESCO.ORG = {
    kdc = adsrv.alfresco.org
    admin_server = adsrv.alfresco.org
 }
 [domain_realm]
 adsrv.alfresco.org = ALFRESCO.ORG
 .adsrv.alfresco.org = ALFRESCO.ORG
```
Note: Specify the realm in uppercase.

Set up the Java login configuration file.

For Tomcat, in the Java security folder (for example, <installLocation>/java/conf/security), create a file named java.login.config with entries as shown in the following example.

Only include ShareHTTP if the server is to run the Share web application (share.war). The AlfrescoHTTP is always needed.

 Alfresco {
    com.sun.security.auth.module.Krb5LoginModule sufficient;
 };
 AlfrescoHTTP
 {
    com.sun.security.auth.module.Krb5LoginModule required
    storeKey=true
    useKeyTab=true
    doNotPrompt=true
    keyTab="C:/etc/http<host>.keytab"
    principal="HTTP/<host>.<domain>";
 };
 ShareHTTP
 {
    com.sun.security.auth.module.Krb5LoginModule required
    storeKey=true
    useKeyTab=true
    doNotPrompt=true
    keyTab="C:/etc/http<host>.keytab"
    principal="HTTP/<host>.<domain>";
 };

 com.sun.net.ssl.client {
    com.sun.security.auth.module.Krb5LoginModule sufficient;
 };

 other {
    com.sun.security.auth.module.Krb5LoginModule sufficient;
 };

To enable the login configuration file, locate and edit the following line in the main Java security configuration file, java\conf\security\java.security.
```
 login.config.url.1=file:/<installLocation>/java/conf/security/java.login.config
```
Note: Make sure that you provide the full file path instead of using variables.
If the Content Services server is not part of the Active Directory domain, ensure that its clock is kept in sync with the domain controller’s, for example, by configuring the domain controller as an NTP server.
To complete the Kerberos SSO tasks on the Alfresco server, see Step 3. Configure Alfresco Share Kerberos SSO.
Use Directory Management in the Repo Admin Console to Configure Kerberos and specify the HTTP password.

Note: Do not change the values of User Config Entry Name and Kerberos Authentication Realm. If you do make a change, the values must match the entries in the Java login configuration file.