File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
The moose likes Websphere and the fly likes wsad 4.0.3 and localos security Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login

Win a copy of Java Interview Guide this week in the Jobs Discussion forum!
JavaRanch » Java Forums » Products » Websphere
Bookmark "wsad 4.0.3 and localos security" Watch "wsad 4.0.3 and localos security" New topic

wsad 4.0.3 and localos security

Tom Cellucci

Joined: Oct 21, 2002
Posts: 2
Does anyone have advice on how to get security enabled for the test environment of WSAD 4.0.3 on Windows 2000? I am editing the server-config.xml using WSAD's editor; checking the "Enable security" checkbox and providing a valid username/password for WSAD on the local box. This causes the server to fail during startup as follows:
JSAS0240E: Login failed. Verify the userid/password is correct. Check the properties file to ensure the login source is valid. If this error occurs on the server, check the server properties to ensure the principalName has a valid realm and userid.
Not sure what else I can do to get WSAD to authenticate, besides checking the box and giving valid username and password. I've tried using the 'Administrator' username, 'domain\Administrator', etc. with no success.
srinivas nedunuri

Joined: Dec 11, 2002
Posts: 16
We get a similar (possibly identical) message but when I use CustomRegistry. I'm stil fishing for possible solutions, but meanwhile...
We have had no difficulty getting local OS based to work. Make sure that in the Security Console, you have the login id + password set correctly (for some reason it asks you for them again the next time you restart the Admin Service). Also, be sure you have defined at least one role for the App (best done using the Application Assembly tool), and that you have made the above login id a member of that role. Once you've done that, you need to restart the admin service and next time it starts up it ought to prompt you for the id + password. You can confirm that your changes were made by opening sas.server.props (located in $WAS_HOME/properties), and making sure that is set to true, and the and are as you set them
[ January 06, 2003: Message edited by: srinivas nedunuri ]

<i>Truth is one; the wise call it by many names</i> (Rig Veda I.64.46)
I agree. Here's the link:
subject: wsad 4.0.3 and localos security
It's not a secret anymore!