Functions For Handling Passwords - Netscape DIRECTORY SERVER 6.1 - PLUG-IN Manual

• 0 if successful.
• -1 if an error occurs (for example, if an invalid ID is specified).
Memory Concerns
The value to be passed in must always be a pointer, even for integer arguments.
For example, if you wanted to do a search with the
int managedsait = 1;
...
slapi_pblock_set(pb, SLAPI_MANAGEDSAIT, &managedsait);
A call similar to the following example will cause a crash:
slapi_pblock_set(pb, SLAPI_MANAGEDSAIT, 1);
However, for values which are already pointers (
**arrays
char *target_dn = slapi_ch_strdup(some_dn);
slapi_pblock_set(pb, SLAPI_TARGET_DN, target_dn);
OR
slapi_pblock_set(pb, SLAPI_TARGET_DN, NULL);
With some compilers, you will have to cast the value argument to (
caller allocates the memory passed in, the caller is responsible for freeing that
memory. Also, it is recommended to use
value to free rather than relying on a potentially dangling pointer. See the
slapi_pblock_get()
When setting parameters to register a plug-in, the plug-in type must always be set
first, since many of the plug-in parameters depend on the type. For example, set the
SLAPI_PLUGIN_TYPE
operation OIDs for the plug-in.
See Also
slapi_pblock_get()

Functions for Handling Passwords

This section contains reference information on routines for handling passwords.
The routines are listed in Table 15-22.
, , etc.), you can pass in the value directly. For example:
Slapi_Backend *
example for more details.
to extended operation before setting the list of extended
Functions for Handling Passwords
ManageDSAIT
char * strings
slapi_pblock_get()
Chapter 15
control:
,
char
). If the
void *
to retrieve the
Function Reference 425