Our Community is getting an upgrade! To get everything ready for the relaunch, we’ll be placing the site in read-only mode starting September 21st.
We really appreciate your understanding while we get things set up behind the scenes. Catch up on all the exciting details about the move here.
Need help or have questions? Drop us a line at [email protected]
Created 10-21-2015 01:17 PM
Created 10-21-2015 02:01 PM
@hkropp - if you're talking about automatically prefixing all AD kerberos principal names that are created, it is possible.
See 4.2.5.1g for some description on how specific LDAP attributes can be modified on creation for each of the principals (if necessary), and 4.2.1.8 on our default prefix which is the name of the cluster.
Created 10-21-2015 01:30 PM
If this is for a Kerborized cluster, you can create rules in the auth_to_local setting under the REALMS configuration section of the krb5.conf file. You would have to tinker with the Advanced krb5 configuration settings in Ambari to create and propogate the rules. The rules can use the incoming AD id and manipulate it as you need. The MIT documentation has a few examples at http://web.mit.edu/kerberos/krb5-1.12/doc/admin/conf_files/krb5_conf.html
Created 10-21-2015 02:01 PM
@hkropp - if you're talking about automatically prefixing all AD kerberos principal names that are created, it is possible.
See 4.2.5.1g for some description on how specific LDAP attributes can be modified on creation for each of the principals (if necessary), and 4.2.1.8 on our default prefix which is the name of the cluster.
Created 10-21-2015 02:27 PM
What about CN or sAMAccount? As I understand they will be the same as principal name, or?
Created 10-21-2015 02:35 PM
Each can be altered independently in the Attribute Template:
When you run through the wizard you'll see the template and the CN, and sAMAccountName and where you have the opportunity to prepend, append, alter their values.