|
This is from the user guide installed when you install client access.--
Use this command from a command prompt to cache user ID password
information on the PC for the specified server. This, in conjunction with
configuring a default user ID for a connection, can be used to provide
automatic logon to a server without the need for iSeries Access for Windows
to display a signon dialog prompt.
Syntax
To signon to a server:
CWBLOGON system /u userid /p password
To clear a specific userid:
CWBLOGON system /u userid /c
To clear all userids from a server:
CWBLOGON system /c
To clear all userids from the cache:
CWBLOGON /c
Parameters
system designates the server name for which to store the user ID and
password information
/u userid designates the server user ID to store in the iSeries
Access for Windows cache
/p password designates the server password associated with user ID
provided
/c clears user ID and password information from the iSeries Access for
Windows cache
Notes
To cache the user ID and password for a system, the system, /u and /p
parameters must be specified. The system name must always be the first
parameter. When using the /c parameter, you can clear a specific userid for
a system, all userids for a system, or all entries in the cache.
If the password value contains embedded blanks, enclose it with double
quotation marks. If the server is configured to support longer mixed case
password values, ensure you specify the password in the exact case it is
defined. If the password value contains double quotes and embedded blanks,
you need to prefix each embedded double quote with the backslash character.
This command can be used to simulate persistent password caching. Running
a batch file when starting your Windows operating system (containing
CWBLOGON invocations) could be used to prime the iSeries Access for Windows
password cache allowing automatic connections to be made.
Passwords cached with this command are only remembered for the duration of
the Windows session, and are deleted when you log off Windows.
Warnings
Because the intent of this command is to provide automatic access to a
sever (i.e. no iSeries signon dialog), be sure to use appropriate security
measures on the PC.
Use appropriate security measures in using this command from batch files.
Invocations provide a server password in clear text format. These passwords
would remain only as secure as access to the batch files themselves.
Recovery
The ERRORLEVEL value indicates whether this command was successful or not.
Examples
CWBLOGON system1 /u myuserid /p mypwd
CWBLOGON system2 /u myuserid /p "Case Sensitive Pwd With Embedded Blanks"
CWBLOGON system3 /u myuserid /p "pwd with one \" embedded quote"
CWBLOGON system1 /u myuserid /c
CWBLOGON system2 /c
CWBLOGON /c
Thanks,
Jay Jernigan
Alamance Regional Medical Center
Financial Analyst
jjernigan@xxxxxxxx
336-538-8299
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:
midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Ashish Kulkarni
Sent: Wednesday, August 12, 2009 10:13 AM
To: midrange-l@xxxxxxxxxxxx
Subject: How to auto login from client access
Hi
Does anyone know how to setup client access for auto login, can i store
as400 name, user id, password some where and read it when starting client
access?
I dont want to make AS400 user is password and windows user id password
same, i already have EIM working for some users, but not possible to extend
to all the end users.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
______________________________________________________________________
Notice: The information contained in this message (Including attachments)
is covered by the Electronic Communications Privacy Act, 18 U.S.C.
2510-2521, is confidential and may be legally protected from disclosure. If
you are not the intended recipient, or an employee or agent responsible for
delivering this message to the intended recipient, you are hereby notified
that any retention, dissemination, distribution or copying of this
communication is strictly prohibited. If you have received this
communication in error, please notify the Sender immediately by replying to
the message and deleting it from your computer.
______________________________________________________________________
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
