| | |
| | | provided ASN.1 element as an LDAP bind request protocol op because the \ |
| | | authentication info element had an invalid BER type (expected 80 or A3, got \ |
| | | %x) |
| | | MILD_ERR_LDAP_BIND_REQUEST_DECODE_CREDENTIALS_82=Cannot decoded the provided \ |
| | | MILD_ERR_LDAP_BIND_REQUEST_DECODE_CREDENTIALS_82=Cannot decode the provided \ |
| | | ASN.1 element as an LDAP bind request protocol op because an unexpected error \ |
| | | occurred while trying to decode the authentication info element: %s |
| | | MILD_ERR_LDAP_COMPARE_REQUEST_DECODE_SEQUENCE_83=Cannot decode the provided \ |
| | |
| | | trying to decode the DN %s used for internal operations as a root user: %s |
| | | INFO_LDAP_CONNHANDLER_DESCRIPTION_SSL_ENABLED_PROTOCOLS_265=Names of the \ |
| | | SSL protocols that will be allowed for use in SSL or StartTLS \ |
| | | communication. Changes to this configuration attribute will take immediately \ |
| | | but will only impact new SSL/TLS-based sessions created after the change |
| | | communication. Changes to this configuration attribute will take effect \ |
| | | immediately but will only impact new SSL/TLS-based sessions created after \ |
| | | the change |
| | | SEVERE_ERR_LDAP_CONNHANDLER_CANNOT_DETERMINE_SSL_PROTOCOLS_266=An unexpected \ |
| | | error occurred while processing the ds-cfg-ssl-protocol attribute in \ |
| | | configuration entry %s, which is used to specify the names of the SSL \ |
| | |
| | | MILD_ERR_LDAP_INTERMEDIATE_RESPONSE_DECODE_INVALID_ELEMENT_COUNT_315=Cannot \ |
| | | decode the provided ASN.1 element as an LDAP intermediate response protocol \ |
| | | op because the request sequence had an invalid number of elements (expected \ |
| | | 0, 1, or or 2, got %d) |
| | | 0, 1, or 2, got %d) |
| | | MILD_ERR_LDAP_INTERMEDIATE_RESPONSE_CANNOT_DECODE_OID_316=An error occurred \ |
| | | while attempting to decode the intermediate response OID: %s |
| | | MILD_ERR_LDAP_INTERMEDIATE_RESPONSE_CANNOT_DECODE_VALUE_317=An error occurred \ |