Re: Single Signon via EIM

We were in that boat a few months ago, but we figured it out.

Kerberos support in Client Access requires that the client, iSeries, and
Kerberos server all map the iSeries IP address back to the same
hostname.

CODE complicates matters by putting entries in the hosts file, like so:

192.168.0.1 R0TARCOM

You can restore the ability to use Kerberos by editing your hosts file
so that the proper host name appears first:

192.168.0.1 real.host.name R0TARCOM

That way CODE and Kerberos are both happy.

-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx

[mailto:wdsci-l-bounces@xxxxxxxxxxxx]

On Behalf Of Justin Taylor
Sent: Thursday, August 30, 2007 9:40 AM
To: wdsci-l@xxxxxxxxxxxx
Subject: [WDSCI-L] Single Signon via EIM

We are working on setting up Single Signon using Enterprise Identity
Management (EIM) and were told by IBM that it is not possible on any

PC

that runs WDSc. This is due to the fact that WDSc requires entries in
the HOSTS file that preclude EIM from working. Does anyone have any
more info on this? Are there any plans to eliminate this restriction?
--
This is the Websphere Development Studio Client for iSeries (WDSCI-L)
mailing list
To post a message email: WDSCI-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/wdsci-l.