

Connector Guides › Connectors Guide › Connecting to Endpoints › Kerberos Connector › Kerberos Connector Limitations › Naming Limitations › Password Policy Naming Limitations
Password Policy Naming Limitations
- kadmin uses the double quote character (“) only as a quoting character. kadmin does not accept this character as part of a password policy name. Thus this connector will reject password policy names containing this character.
- kadmin will accept a password policy name that starts with a hash (#). However, due to DN syntax limitations, the hash at the beginning of a name will be escaped with a backslash character. Within the Provisioning Manager and the Kerberos system, this escape character will always be present.
Copyright © 2013 CA.
All rights reserved.
 
|
|