Specifying How iProcess Validates Users

Lines 15 and 16 of the staffpms file define whether and how iProcess uses the integral User Validation API provided with the LDAPCONF utility.

Specifying an External User Validation Package

Line 15 defines whether the iProcess Suite validates users against O/S user accounts (the default), or against an external validation package developed using the TIBCO iProcess User Validation API.

This line is optional. If you are using the default method of validating users against O/S accounts, line 15 should be blank.

If you want to validate users against an external validation package, line 15 must contain the full pathname of the user validation package (a DLL file on Windows, a shared library on UNIX). Note that:

•

The pathname must contain a leading drive letter and UNIX style separators (/).

•

Variables such as SWDIR are not supported in this parameter.

The following example (for the iProcess Engine for Windows) specifies that user validation will be performed against the swuvamod.dll file in the D:/iProcess/staff200/lib directory.

d:/iProcess/staff200/lib/swuvamod.dll

The following example specifies that user validation will be performed against the UVAPI.dll file in the C:/Tibco/iprocess_nod1/util directory and that the proxy users are supplied by swadmin.

C:/Tibco/iprocess_nod1/util/UVAPI.dll\N\swadmin\\\

For more information about how to:

•

Develop an external validation package, see TIBCO iProcess User Validation API User's Guide.

•

Install an external validation package, see the Installation guide for TIBCO iProcess User Validation API.

•

Use the integral user validation API provided with LDAPCONF, see LDAPCONF Utility User’s Guide.

Specifying a Proxy User

Line 16 defines which proxy operating system user ID is used by the LDAP integral user validation API.

This line is optional. If you are not using the LDAP integral user validation API, line 16 should be blank.