Client Access Express save password
Bigeasy
We 'upgraded' a few pc's from Client Access 3.2 to Client Access Express 4.5
(because
the older versions are not workung under Windows 2000)
Since then the user has to enter a username and pasword in a popup window
every first time he starts
client access during the day, after which he gets his normal signon.
Previously it was possible to say 'save password' but that box is no longer
there in CAE.
Is it possible to prevent this somehow?
Thanks
Conrad
Fabio
You have to put a .BAT file to save user and password in the STARTUP folder;
in this file you have to use the command CWBLOGON (that you find in the
Client Access folder in your PC).
The syntax is the following:
CWBLOGON <AS name or IP address> /U <user name) /P <password>
In the emulation configuration (you can reach it via Operation Navigator)
you have to set to connect to AS with a specific user, the same you specify
in the .BAT file.
I hope to be helpful. Sorry for my english.
Fabio
From Italy
"Bigeasy" <Conrad...@nospam.gzm.geveke.nl> ha scritto nel messaggio
news:9k604u$5h7$1...@azure.nl.gxn.net...
DRezanka
In the connection properties you can specify "Use Windows logon". I haven't
tried it but the help text says it works. Of course the Windows
logon/password would have to match the AS400 logon/password.
best wishes,
Doug
"Bigeasy" <Conrad...@nospam.gzm.geveke.nl> wrote in message
news:9k604u$5h7$1...@azure.nl.gxn.net...
Barry Wright
sign on that first time. Using a batch file to "pre-logon" is one option,
but it does leave passwords in the clear in the batch file. That is a
matter of your corporate policy over whether that is a risk that you are
willing to take. In my company, we would never do that.
Barry
"Bigeasy" <Conrad...@nospam.gzm.geveke.nl> wrote in message
news:9k604u$5h7$1...@azure.nl.gxn.net...
Richard White
"Fabio" <fabio.da...@dallagnese.it> wrote in message
news:9k63l9$2hg8r$1...@ID-100148.news.dfncis.de...
> It's the same using Win NT.
> You have to put a .BAT file to save user and password in the STARTUP
folder;
> in this file you have to use the command CWBLOGON (that you find in
the
> Client Access folder in your PC).
> The syntax is the following:
>
> CWBLOGON <AS name or IP address> /U <user name) /P <password>
This is absolutely CRAZY !!
IBM has obviously decided that password security on PC's which access
AS/400s is a thing of the past.
Since when would any sane IS Manager allow insecure AS/400 passwords?
[...snipped...]
> I hope to be helpful. Sorry for my english.
No problem with your English Fabio :-)
The other big "improvement" in CA Express is the total botch job on
Network Drive/Printer support.
Even working on a LAN it's next to impossible to set up ..... even IBM
Support only managed to get me as far as having to search for my AS/400
by IP address (in Win2K) and then latch on to it. Trying to get
Network Drives to an AS/400 over an internet connection is well nigh
impossible.
Perhaps in Version 5 CA Express will give me a working solution to both
these problems?
Geveke
I implemented Fabio's suggegtion like this:
I created a 'connection only' user on the AS/400 called PCUSER with password
PCUSER with an
initial program *SIGNOFF so it cannot be used interactively.
I created a batch file in the startup group that does a CWBLOGON AS400 /u
PCUSER /p PCUSER
So with this solution no security issue occured and it's easy for the user!
Thanks Fabio for putting me on the right track, thanks others for the other
suggestions
Conrad
----------------------------------------------------------------------------
---------------
"Fabio" <fabio.da...@dallagnese.it> wrote in message
news:9k63l9$2hg8r$1...@ID-100148.news.dfncis.de...
wmca...@earthlink.net
> So does anyone know this little diddy on the password thing..
>
> Ideally, we'd use the Windows password/login for the AS/400. But
> guess what...I think the AS/400 is limited to the number of characters
> in the login / password
>
> So...if we for example had a user..I'll make up a name:
>
> rvandenhout
>
> we'd have to use something shorter. And then the lovely thing about
> that is that the e-mail address would then be shorter if we used
> things the same across the board.
>
> When will the 400 play nice with other things? Sometimes it acts
> like it wants to be a legacy box. Yes, MS stuff isn't so great, but
> the 400 should make it easier to manage passwords and not be length
> limited.
Actually, V5R1 of OS400 supports passwords up to 128 characters. Passwords can
consist of any keyboard characters, including blanks, and are case sensitive.
The only restriction is that it can't be all blanks.
No One
> > CWBLOGON <AS name or IP address> /U <user name) /P <password>
>
> This is absolutely CRAZY !!
> IBM has obviously decided that password security on PC's which access
> AS/400s is a thing of the past.
>
> Since when would any sane IS Manager allow insecure AS/400 passwords?
>
Actually, the ability to cache passwords was a Microsoft feature in
Win9x/ME
that does not exist in Windows NT or 2000. The ability to cache or not
cache
passwords has nothing to do with your Client Access release.
The Microsoft password cache (PWL files) is, in itself, insanely easy to
break and is barely more secure than using the passwords in the open
using CWBLOGON.
The best compromise in many cases is to have the user's Windows and
AS/400 IDs and passwords match, then choose to have Client Access use
the Windows logon for signon. Windows 2000 passwords are significantly
safer than the old PWL files from Win9x, and the password cracking tools
I've seen for WIndows NT/2000 all either did not word or required the user
to already be logged into the PC with administrator rights.
.
To set the connection options, right click on the AS/400 system name in
Operations Navigator and choose "Properties" from te context menu. The
setting in question is on the connection tab.