Here you can find the error codes for LDAP described here.
Indicates an internal error. The server is unable to respond with a more specific error and is also unable to properly respond to a request. It does not indicate that the client has sent an erroneous message. In NDS 8.3x through NDS 7.xx, this was the default error for NDS errors that did not map to an LDAP error code. To conform to the new LDAP drafts, NDS 8.5 uses 80 (0x50) for such errors.
Indicates that the server has received an invalid or malformed request from the client.
Indicates that the operation’s time limit specified by either the client or the server has been exceeded. On search operations, incomplete results are returned.
Indicates that in a search operation, the size limit specified by the client or the server has been exceeded. Incomplete results are returned.
Does not indicate an error condition. Indicates that the results of a compare operation are false.
Does not indicate an error condition. Indicates that the results of a compare operation are true.
Indicates that during a bind operation the client requested an authentication method not supported by the LDAP server.
Indicates one of the following: In bind requests, the LDAP server accepts only strong authentication.In a client request, the client requested an operation such as delete that requires strong authentication. In an unsolicited notice of disconnection, the LDAP server discovers the security protecting the communication between the client and server has unexpectedly failed or been compromised.
Does not indicate an error condition. In LDAPv3, indicates that the server does not hold the target entry of the request, but that the servers in the referral field may.
Indicates that an LDAP server limit set by an administrative authority has been exceeded.
Indicates that the LDAP server was unable to satisfy a request because one or more critical extensions were not available. Either the server does not support the control or the control is not appropriate for the operation type.
Indicates that the session is not protected by a protocol such as Transport Layer Security (TLS), which provides session confidentiality.
Does not indicate an error condition, but indicates that the server is ready for the next step in the process. The client must send the server the same SASL mechanism to continue the process.
Indicates that the attribute specified in the modify or compare operation does not exist in the entry.
Indicates that the attribute specified in the modify or add operation does not exist in the LDAP server’s schema.
Indicates that the matching rule specified in the search filter does not match a rule defined for the attribute’s syntax.
Indicates that the attribute value specified in a modify, add, or modify DN operation violates constraints placed on the attribute. The constraint can be one of size or content (string only, no binary).
Indicates that the attribute value specified in a modify or add operation already exists as a value for that attribute.
Indicates that the attribute value specified in an add, compare, or modify operation is an unrecognized or invalid syntax for the attribute.
Indicates the target object cannot be found. This code is not returned on following operations: Search operations that find the search base but cannot find any entries that match the search filter. Bind operations.
Indicates that an error occurred when an alias was dereferenced.
Indicates that the syntax of the DN is incorrect. (If the DN syntax is correct, but the LDAP server’s structure rules do not permit the operation, the server returns LDAP_UNWILLING_TO_PERFORM.)
Indicates that the specified operation cannot be performed on a leaf entry. (This code is not currently in the LDAP specifications, but is reserved for this constant.)
Indicates that during a search operation, either the client does not have access rights to read the aliased object’s name or dereferencing is not allowed.
Indicates that during a bind operation, the client is attempting to use an authentication method that the client cannot use correctly. For example, either of the following cause this error: The client returns simple credentials when strong credentials are required…OR…The client returns a DN and a password for a simple bind when the entry does not have a password defined.
Indicates that during a bind operation one of the following occurred: The client passed either an incorrect DN or password or the password is incorrect because it has expired, intruder detection has locked the account or another similar reason. See the data code for more information.
Indicates that the caller does not have sufficient rights to perform the requested operation.
Indicates that the LDAP server is too busy to process the client request at this time but if the client waits and resubmits the request, the server may be able to process it then.
Indicates that the LDAP server cannot process the client’s bind request, usually because it is shutting down.
Indicates that the LDAP server cannot process the request because of server-defined restrictions. This error is returned for the following reasons: The add entry request violates the server’s structure rules…OR…The modify attribute request specifies attributes that users cannot modify…OR…Password restrictions prevent the action…OR…Connection restrictions prevent the action.
Indicates that the client discovered an alias or referral loop, and is thus unable to complete this request.
Indicates that the add or modify DN operation violates the schema’s structure rules. For example,The request places the entry subordinate to an alias. The request places the entry subordinate to a container that is forbidden by the containment rules. The RDN for the entry uses a forbidden attribute type.
Indicates that the add, modify, or modify DN operation violates the object class rules for the entry. For example, the following types of request return this error:The add or modify operation tries to add an entry without a value for a required attribute. The add or modify operation tries to add an entry with a value of an attribute which the class definition does not contain. The modify operation tries to remove a required attribute without removing the auxiliary class that defines the attribute as required.
Indicates that the requested operation is permitted only on leaf entries. For example, the following types of requests return this error:The client requests a delete operation on a parent entry. The client requests a modify DN operation on a parent entry.
Indicates that the modify operation attempted to remove an attribute value that forms the entry’s relative distinguished name.
Indicates that the add operation attempted to add an entry that already exists, or that the modify operation attempted to rename an entry to the name of an entry that already exists.
Indicates that the modify operation attempted to modify the structure rules of an object class.
Reserved for CLDAP.
Indicates that the modify DN operation moves the entry from one LDAP server to another and requires more than one LDAP server.
Indicates an unknown error condition. This is the default value for NDS error codes which do not map to other LDAP error codes.
Updated almost 3 years ago