VerifyBinderyObjectPassword

Verifies that the password of a bindery object is valid (For cross-platform functionality, see Developing NLMs with Cross-Platform Functions ( NDK: NLM Development Concepts, Tools, and Functions) and call NWVerifyObjectPassword)

Local Servers:blocking
Remote Servers:blocking
Classification:3.x, 4.x, 5.x, 6.x
Service:Server-Based Bindery

Syntax

   #include <\nlm\nit\nwbindry.h>  
    
   int VerifyBinderyObjectPassword (  
      char   *objectName,  
      WORD   objectType,  
      char   *password); 
   

Parameters

objectName
(IN) Specifies the string containing the name of the bindery object (maximum 48 characters, including the NULL terminator).
objectType
(IN) Specifies the type of the bindery object (OT_USER, OT_GROUP, OT_PRINT_SERVER, and so on).
password
(IN) Specifies the string containing the password to be checked (maximum 128 characters; must be uppercase; NULL string = no password).

Return Values

0

(0x00)

ESUCCESS

150

(0x96)

ERR_SERVER_OUT_OF_MEMORY

240

(0xF0)

ERR_WILDCARD_NOT_ALLOWED

251

(0xFB)

ERR_NO_SUCH_PROPERTY

252

(0xFC)

ERR_NO_SUCH_OBJECT

254

(0xFE)

ERR_SERVER_BINDERY_LOCKED

255

(0XFF)

ERR_NO_SUCH_OBJECT_OR_BAD_PASSWORD

Remarks

This function verifies the password of a bindery object by passing the objectName, objectType, and password parameters.

The objectName and objectType parameters must uniquely identify the bindery object and must not contain wildcard characters. The objectName can be from 1 to 48 characters long, including the NULL terminator. Only printable characters can be used. Slashes, backslashes, colons, semicolons, commas, asterisks, and question marks are prohibited.

There is a distinction between a bindery object without a password property and a bindery object with a password property that has no value. An entity is not allowed to log in to a server as a bindery object that does not have a password property. However, an entity is allowed to log in to a server as a bindery object that has a password property with no value. This function does not require that the requesting entity be logged in to the server.

If the object does not have a password property then the check fails. If the object has a password of length zero, a password of length zero matches.

See Also

ChangeBinderyObjectPassword