- <!--<prop key="kdc.entryBaseDn">ou=users,dc=example,dc=com</prop>-->
- <!--<prop key="kdc.java.naming.security.credentials">secret</prop>-->
- <!--
- <prop key="changepw.entryBaseDn">ou=users,dc=example,dc=com</prop>
- -->
- <!--
- <prop key="changepw.java.naming.security.credentials">secret</prop>
- -->
- <!--
- Set this key to a space delimited set of attributeType descriptions
- and their OID's if you want an attributeType to be handled as
- binary content. The server will use the schema to derive the set of
- attributeTypes to treat as binary. The union if the values you
- provide here will be taken as the set of binaries. Note to be
- consistent you must add both the OID and all the names an
- attributeType can have.
- -->
- <!--
- <prop key="java.naming.ldap.attributes.binary"></prop>
- -->
+ <!--<prop key="kdc.entryBaseDn">ou=users,dc=example,dc=com</prop> -->
+ <!--<prop key="kdc.java.naming.security.credentials">secret</prop> -->
+ <!-- <prop key="changepw.entryBaseDn">ou=users,dc=example,dc=com</prop> -->
+ <!-- <prop key="changepw.java.naming.security.credentials">secret</prop> -->
+ <!-- Set this key to a space delimited set of attributeType descriptions
+ and their OID's if you want an attributeType to be handled as binary content.
+ The server will use the schema to derive the set of attributeTypes to treat
+ as binary. The union if the values you provide here will be taken as the
+ set of binaries. Note to be consistent you must add both the OID and all
+ the names an attributeType can have. -->
+ <!-- <prop key="java.naming.ldap.attributes.binary"></prop> -->