Re: Client\User Security Problem

kastanek

Well Known Member
Re: Client\\User Security Problem

I've seen a similar thing where when Client Access Express is installed you
have three options for Default User ID: Use Windows User ID, Use Default
(specify) or Prompt everytime. When OneWorld connects to the Database it
first needs to connect to the AS/400 through Client Access. If you said
Prompt Everytime when CA/400 was installed you get your issue. Try looking
to see what the Client Access Connection Settings are. You get the same
thing when you just try to launch a Green Screen Session but you only get
asked for the connection user ID and password once per PC Boot. Once
signed on the issue goes away until you reboot again.

Try rebooting a machine and then connecting to a Green Screen session.
Once connected try OneWorld and see if you have the issue. If not then
that is your problem - CA/400 connectivity.

Good luck!

Regards,
Gerald.






jenningp
<jenningp@timken. To: Gerald Kastanek/Toronto/IBM@IBMCA
com> cc:
Sent by: Subject: Client\User Security Problem
owner-jdelist@jde
list.com


10/08/2002 01:25
PM
Please respond to
jdelist





Can somebody point me in the right direction?

Oneworld 733.2, AS400 Enterprise Server, FAT Clients

Security Server enabled on both server and clients as well as within OW.
Win98 clients connect OK. Win 2000 client asks for the system user password
after every reboot (password cache flushed), which if supplied, allows the
application to function correctly. All users are set up with the correct
system user and pw combination. It appears to me that our Win98 clients
connect from cold OK due to Win9x password saving (supplied after initial
workstation install), a facility that 2000 doesn't provide. It is my
understanding that neither password saving for Win9x or manually entering
the pw on 2000 should be required. Correct me if I'm wrong but shouldn't
the process work as follows. OW executed and network functional, user
enters OW username and pw. This is passed to an enterprise server kernel.
This process or sub process checks the validity of the data passed to it
against the !
OW098SEC table. If the user exists and the password is correct the Kernel
process returns the system user/s and password/s to the client. These are
then cached for the length of a users OW session and are used to connect to
required data via the relevant ODBC connection. Is this correct??? Where
can things be going wrong? What am I missing??

Any help would be much appreciated

Thanks in Advance

Paul
--------------------------
To view this thread, go to:
http://www.jdelist.com/ubb/showthreaded.php?Cat=&Board=OW&Number=43146
+ - - - - - - - - - - - - - - - - - - - - - - - -+
This is the JDEList One World® / XE mailing list/forum.
Archives and information on how to SUBSCRIBE, and
UNSUBSCRIBE can be found on the JDEList Forum at
http://www.JDEList.com

JDEList is not affiliated with JDEdwards®

+ - - - - - - - - - - - - - - - - - - - - - - - -+
 
Re: Client\\User Security Problem

Thanks for the response. As far as CA goes all AS400 ODBC connection settings are the same and use the ops navigator default and the same security. I know i'm doing something wrong somewhere. Im pretty inexperienced at JDE OW, learning as I go along so theres probably something quite fundamental missing. This area has never worked properly since being installed by external consultants and im now slowly going through the system trying to tighten things up.
 
Back
Top