KB-6351: How to Configure adclient To Create A Kerberos Ticket Using Lower Case Letters For the Default Principal In Hierarchical and Classic Zones?

Home >

KB-6351: How to Configure adclient To Create A Kerberos Ticket Using Lower Case Letters For the Default Principal In Hierarchical and Classic Zones?

Product:

Centrify DirectControl ,

Published:

9 March,16 at 06:15 PM

Rating:

Applies to:

Centrify Server Suite 2016

Question:

When adclient obtains a kerberos credential (joe@<REALM>), it will use UPN by default, with alternative sAMAccountName. The kerberos ticket is case sensitive. If the UPN or sAMAccountName is in upper case, then the ticket will reflect so.

For Example:

upn: Joe@centrifyimage.vms
sAMAccountName: Joe

Joe logs in and creates a kerberos ticket:

[joe@engcen6 ~]$ klist -A
Ticket cache: FILE:/tmp/krb5cc_cdc1627391098_g36QnZ
Default principal: Joe@CENTRIFYIMAGE.VMS

Some applications, including Hadoop, require the default principal to be in all lower case letters. Centrify has the option to force the kerberos principal to lower case letters for auto-zone:

auto.schema.name.lower: true

How can the Centrify Agent be configured to force lower case letters for the kerberos principal in hierarchical and classic zones types?

Answer:

A new parameter is available starting in Suite 2016. In /etc/centrifydc/centrifydc.conf

adclient.krb5.principal.lower: true

The default value is false.

To implement:

1) Set the value of the parameter in /etc/centrifydc/centrifydc.conf
adclient.krb5.principal.lower: true
2) # adreload
3) # adflush -f

Now when Joe logs in and creates a kerberos ticket the default principal is in lower case letters:

[joe@engcen6 ~]$ klist -A
Ticket cache: FILE:/tmp/krb5cc_cdc1627391098_pITwFK
Default principal: joe@CENTRIFYIMAGE.VMS

This same parameter also works when the sAMAccountName is used as the principal value.
i.e.
adclient.krb5.principal: sam
adclient.krb5.principal.lower: true