> Option 2: Oh, darn...Option 1 didn't work. And we cannot ditch LDAP > authentication. > > Create a local special UNIX user in your server side (meaning, the > user's password stored in traditional UNIX password file with crypted > password in password field) > > 1. In your client application, authenticate connecting users using JNDI > if your application is written in JAVA or ADSI if your application is > written in Visual Basic (System.Directoryservices for .NET) before > calling UniObject routines. > 2. Use that special UNIX user to open a UniObject session. > > Bad (?) thing about the above implementation is that the special user > will be an owner of a file, not actual user, when writing a record.
Or, options 3, email me off list for details of our U2 native LDAP authentication and query routines.
Craig ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
