RE: Websphere authenticating to a remote as/400 and Envoy

Todd,

You can authenticate to LDAP but I haven't done it with WebSphere. With
Tomcat you can use the JNDI realm, which is pretty quick to set up. If
you are not running natively on the iSeries the only way to pass the
authentication is through Kerberos (or a password, which is
sub-optimal). Running natively, you can use the POSIX
SetEffectiveUser/Group API's to achieve the same thing. Pat Botz has
written quite a bit on this topic. Here is one article on single
sign-on: http://www.midrangeserver.com/tfh/tfh081903-story04.html.

>>> tbryant@xxxxxxxxxxxxxxxxxxxxxxx 4/21/2004 8:56:23 AM >>>
Thank you very much Joe and David for your insight. 

Here at work we had discussed using an LPAD system on the 400. The 400
admin
has told me that it is possible to use an LDAP repository instead of
user
profiles for authentication. We also run a windows network. From what I
am
told, the 400 can be set up to use a remote LDAP repository for storage
of
user information. We were going to see if we could use the Active
Directory
LDAP repository in windows for all our user info. This way if someone
tried
to log on to either the 400 or the windows network they would be
authenticating against the same information. Users would also only have
to
change their password in one place without remembering two different
signons. This would also solve the problem of moving the Websphere
server to
a windows box as the current user information from the 400 would be in
Active Directory. 

Does anyone have any idea if this is feasible?