What is iProcess User Validation?

The default method of user validation in the TIBCO iProcess Engine requires you to create operating system accounts for each registered iProcess user. Also, the login passwords are maintained by the operating system.

If you have different security validation requirements, you can use the User Validation API to create your own method of user validation to match your business needs. For example, you might want to create operating system users but have a different form of password validation. Alternatively, you might want to completely separate the users and their passwords from the operating system by maintaining them in a database of your choice.

The User Validation API provides interfaces that you can use to maintain your list of iProcess users and their passwords. It essentially isolates iProcess from validating users against the operating system so that you can provide your own user identity and validation system.

 

Note	The following core iProcess users are still required as operating system accounts.

 

O/S Account	Windows (SQL Server or Oracle)	UNIX/Oracle	UNIX/DB2
IPEBAKGROUND , where, IPEBAKGROUND indicates the UNIX user account that owns most iProcess Engine files and is used to run the iProcess Engine background processes. (Not used on Windows.	n/a	Required	Required
IPEADMIN, where, IPEADMIN indicates the operating system account that is used to administer the iProcess Engine node.	Required	Required	Required
IPESERVICE, where, indicates the Windows account that is used to run the iProcess Engine node (Not used on UNIX.).	Required	n/a	n/a
iProcess Engine DB Schema Owner	n/a	n/a	Required
iProcess Engine DB user	n/a	n/a	Required