wsadmin and security enabled

[Rainer Freis]

Hello,

I enabled security in WebSphere 5.1 (Network Deployment). Now when I
use
wsadmin I have to authenticate myself.

When I give username and password on the command line like

./wsadmin.sh -user exampleuid -password examplepw -f testcsript.jacl

everything works fine.

As I don't want to type username and password all the time I created a
wsadmin.properites file in my home directoy where I set

com.ibm.SOAP.securityEnabled=true
com.ibm.SOAP.loginUserid=exampleid
com.ibm.SOAP.loginPassword=examplepw
com.ibm.ws.scripting.traceFile=/tmp/wsadmin.trace
com.ibm.ws.scripting.validationOutput=/tmp/wsadmin.valout

Now the locations for the output files are read from my properties
file but password and userid doesn't work and I get an error:

./wsadmin -f testscript.jacl

WASX7246E: Cannot establish "SOAP" connection to host "localhost"
because of an authentication failure. Ensure that user and password
are correct on the command line or in a properties file.

Any idea why user and password entries don't work?

regards

Rainer

[Raphael De La Torre]

Hi,

I did something similar to this before. However, my userid and
password were contained in a different file. I'll post the snippet of
the batch file I used.

The file login.properties contains the user id and password delimited
by a carriage return.

The batch file I use to kick off the jacl files contain these lines to
get the user id and password.

set VAR=login.properties
for /F "skip=1 eol= tokens=*" %%S in (%VAR%) do (set
userid=%%S&goto:useridfor)
:useridfor
for /F "skip=2 eol= tokens=*" %%S in (%VAR%) do (set
password=%%S&goto:pwdfor)
:pwdfor

The actual call to execute the jacl file looks like this:
wsadmin -f myJaclFile.jacl -user %userid% -password %password%

Hope this helps you out.

Raphael T. De La Torre
Software Engineer

TechFlow Inc.
12220 El Camino Real
Suite 300
San Diego, CA. 92130
(858) 481-1125 x117
rdela...@techflow.com

rainer...@web.de (Rainer Freis) wrote in message news:<e2a19476.04021...@posting.google.com>...

[Victor Yongwei Yang]

Another documented way from IBM is:

"If you use a Simple Object Access Protocol (SOAP) connector, set the
following properties in the soap.client.props file with the
appropriate values:
com.ibm.SOAP.securityEnabled=true
com.ibm.SOAP.loginUserid=
com.ibm.SOAP.loginPassword= "

For ND, if you run wsadmin.sh from Deployment Manager's
/usr/WebSphere/DeploymentManager/bin, you should use the
soap.client.props under /usr/WebSphere/DeploymentManager/properties

Also note whatever is supplied on the cmd line of wsadmin will
override the
setting in soap.client.props.

For RMI connector, it uses sap.client.props instead as default.

Hope it helps.

Victor

[Rainer Freis]

Hello,

pytho...@yahoo.com (Victor Yongwei Yang) wrote in message news:<fee98265.0402...@posting.google.com>...

> Another documented way from IBM is:
>
> "If you use a Simple Object Access Protocol (SOAP) connector, set the
> following properties in the soap.client.props file with the
> appropriate values:
> com.ibm.SOAP.securityEnabled=true
> com.ibm.SOAP.loginUserid=
> com.ibm.SOAP.loginPassword= "
>
> For ND, if you run wsadmin.sh from Deployment Manager's
> /usr/WebSphere/DeploymentManager/bin, you should use the
> soap.client.props under /usr/WebSphere/DeploymentManager/properties
>
> Also note whatever is supplied on the cmd line of wsadmin will
> override the
> setting in soap.client.props.
>

That's clear to me. BUT:

giving the password on the command line is not a good idea as you can
see it with "ps". Adding the password in a file isn't a preferred idea
either - especially as we are several administrators.

So the best solution would be to use a property file in the home
directory as each admin can use his own password.

regards

Rainer