UVAPI

A different approach is to write a customer SPO/SSO based application to insert your users (don't forget to properly configure your server to do that).

UVAPI, as far as I know, are only Validation API, not provided with iPE.They're intended to provide a custom validation procedure to iPE instead of OS or No Validation options.

You should set the DISABLE_USER_CHECK attribute - this disables the check and is quite useful.

The UVAPI is only if you want to implement a custom authorization (e.g.against a user base in your legacy base) and I would definitely not use it as you have to implement a shared library in c (or c++) with a poor interface and no way to do this in Java (using JNI).


Iprocess should have provided a rich API for the authentication or either a web service or some thing that can be hooked onto BW. Also the need to create users at iprocess side is a over head. A configurable authentication method would have been good in this case.


There is also a standard validation against LDAP in the product - an "inbuilt" UVAPI for LDAP. So you can validate against external users without writing C code if you have access to LDAP> And in terms of user information (attributes, group memberships etc) I think you can import that from LDAP too (as well as being able to import it via batch file or APII).

So you neither have to create iPE users manually nor write your own validation code if you have LDAP and can get it configured accordingly.

The current LDAP implementation is far better then the one being implemented with 10.x but in most cases not sufficient because

- a lot of customers don't have LDAP

- need Single-Sign-One


and therefore a Java-based API would be find because we could then simply authenticate the iProcess users against our own system and provide SSO.