Enabling Security in AEs on NT

Ma...@softlanding.com

unread,

Dec 6, 2001, 1:09:41 PM12/6/01

to

I am using the version of AEs that comes with WSAD.

What are the requirements for enabling security in AEs on NT 4.0?

On my machine, it works fine, on another developer's machine it does not.
Both of our ID's are in the local machines Admin group, however my ID is
also in our Domain Admin group. We are both logged in with a Domain
account.

In the Server configuration we are specifying the user name and password
of the Domain Administrator. Again, on my PC it works, on the other PC it

does not. Here is the error we receive when starting the server:

*** Starting the server ***
IBM WebSphere Application Server, Release 4.0.1
Advanced Single Server Edition for Multiplatforms
Copyright IBM Corp., 1997-2001

[01.12.06 10:36:37:759 EST] 59a0738 SASConfig A ORB SSL Key File or
Passwords settings were missing in server-cfg.xml
************ Start Display Current Environment ************
WebSphere AEs 4.0.1 a0131.07 running with process name localhost/Default
Server and process id 348
Host Operating System is Windows NT, version 4.0
Java version = J2RE 1.3.0 IBM build cn130-20010609 (JIT enabled: jitc),
Java Compiler = jitc
server.root = D:/Program Files/IBM/Application
Developer/plugins/com.ibm.etools.websphere.runtime
Java Home = D:\Program Files\IBM\Application
Developer\plugins\com.ibm.etools.server.jdk\jre
ws.ext.dirs = D:/Program Files/IBM/Application
Developer/plugins/com.ibm.etools.server.jdk/lib;D:/Program
Files/IBM/Application
Developer/plugins/com.ibm.etools.websphere.runtime/classes;D:/Program
Files/IBM/Application
Developer/plugins/com.ibm.etools.websphere.runtime/lib;D:/Program
Files/IBM/Application
Developer/plugins/com.ibm.etools.websphere.runtime/lib/ext;D:/Program
Files/IBM/Application
Developer/plugins/com.ibm.etools.websphere.runtime/web/help;D:/Program
Files/IBM/Application
Developer/plugins/com.ibm.etools.websphere.tools/runtime/wasListener.jar;D:/Program

Files/IBM/Application
Developer/plugins/com.ibm.etools.webservice/runtime/worf.jar
Classpath = D:/Program Files/IBM/Application
Developer/plugins/com.ibm.etools.websphere.runtime/properties;D:/Program
Files/IBM/Application
Developer/plugins/com.ibm.etools.websphere.runtime/lib/bootstrap.jar;D:/Program

Files/IBM/Application
Developer/plugins/com.ibm.etools.websphere.tools/runtime/wteServers.jar;D:/Program

Files/IBM/Application
Developer/plugins/com.ibm.etools.websphere.tools/runtime/wasTools.jar
Java Library path = D:/Program Files/IBM/Application
Developer/plugins/com.ibm.etools.websphere.runtime/bin;D:\Program
Files\IBM\Application
Developer\jre\bin;.;C:\WINNT40\System32;C:\WINNT40;D:\Pvcs\VM\win32\bin;D:\IBMDebug\bin;C:\WINNT40\system32;C:\WINNT40;D:\jdk1.2.2\bin;D:\IMNnq_NT;C:\WINNT40\system32;C:\WINNT40;d:\PROGRA~1\IBM\CLIENT~1;d:\PROGRA~1\IBM\CLIENT~1\Shared;d:\PROGRA~1\IBM\CLIENT~1\Emulator;D:\Program

Files\Microsoft Visual Studio\Common\Tools\WinNT;D:\Program
Files\Microsoft Visual Studio\Common\MSDev98\Bin;D:\Program
Files\Microsoft Visual Studio\Common\Tools;D:\Program Files\Microsoft
Visual Studio\VC98\bin;d:\Plex450\bin;
Current trace specification =
************* End Display Current Environment *************
[01.12.06 10:36:38:941 EST] 59a0738 Server U Version : 4.0.1
[01.12.06 10:36:38:941 EST] 59a0738 Server U Edition: Advanced
Single Server Edition for Multiplatforms
[01.12.06 10:36:38:941 EST] 59a0738 Server U Build date: Thu Aug
09 00:00:00 EDT 2001
[01.12.06 10:36:38:941 EST] 59a0738 Server U Build number:
a0131.07
[01.12.06 10:36:47:072 EST] 59a0738 SystemOut U 2> [2001-12-06
10:36:47.062], [ServerID: 1123441223],
[LoginHelperImpl.request_login_controlled]:
[01.12.06 10:36:47:072 EST] 59a0738 SystemOut U 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.
[01.12.06 10:36:47:162 EST] 59a0738 SystemOut U 3> [2001-12-06
10:36:47.082], [ServerID: 1123441223],
[CredentialsImpl.get_mapped_credentials]:
[01.12.06 10:36:47:162 EST] 59a0738 SystemOut U 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.
[01.12.06 10:36:47:192 EST] 59a0738 SystemOut U 4> [2001-12-06
10:36:47.182], [ServerID: 1123441223], [VaultImpl.setServerCred]:
[01.12.06 10:36:47:192 EST] 59a0738 SystemOut U Failed to set
the server type 2 credentials.
[01.12.06 10:36:47:202 EST] 59a0738 SystemOut U 5> [2001-12-06
10:36:47.192], [ServerID: 1123441223],
[LoginHelperImpl.request_login_controlled]:
[01.12.06 10:36:47:202 EST] 59a0738 SystemOut U 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.
[01.12.06 10:36:47:242 EST] 59a0738 SystemOut U 6> [2001-12-06
10:36:47.232], [ServerID: 1123441223],
[CredentialsImpl.get_mapped_credentials]:
[01.12.06 10:36:47:242 EST] 59a0738 SystemOut U 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.
[01.12.06 10:36:47:443 EST] 59a0738 SecurityConte X SECJ0131E:
Authentication failed. Unable to get the mapped credential for
SecOwnCredentials.
[01.12.06 10:36:47:483 EST] 59a0738 StandardIniti X SECJ0007E: Error
during security initialization
[01.12.06 10:36:47:533 EST] 59a0738 StandardServe F WSVR0006E: Server
Default Server failed during initialization : java.lang.Exception:
Authentication Failed
at
com.ibm.ejs.security.SecurityContext.getActualCreds(SecurityContext.java:74)
at
com.ibm.ws.security.core.StandardInitializer.installAdminApp(StandardInitializer.java:200)
at
com.ibm.ws.security.core.StandardInitializer.initialize(StandardInitializer.java:151)
at
com.ibm.ws.runtime.StandardServer.initializeSecurityRuntime(StandardServer.java:390)
at com.ibm.ws.runtime.Server.initializeRuntime0(Server.java:951)
at
com.ibm.ws.runtime.StandardServer.initializeRuntime0(StandardServer.java:341)
at com.ibm.ws.runtime.Server.initializeRuntime(Server.java:882)
at com.ibm.ws.runtime.StandardServer.main(StandardServer.java:519)
at java.lang.reflect.Method.invoke(Native Method)
at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:158)
at
com.ibm.etools.websphere.tools.runner.api.ServerRunner$1.run(ServerRunner.java)

[01.12.06 10:36:47:653 EST] 59a0738 SystemOut U WSVR0006E: Server
Default Server failed during initialization : java.lang.Exception:
Authentication Failed
at
com.ibm.ejs.security.SecurityContext.getActualCreds(SecurityContext.java:74)
at
com.ibm.ws.security.core.StandardInitializer.installAdminApp(StandardInitializer.java:200)
at
com.ibm.ws.security.core.StandardInitializer.initialize(StandardInitializer.java:151)
at
com.ibm.ws.runtime.StandardServer.initializeSecurityRuntime(StandardServer.java:390)
at com.ibm.ws.runtime.Server.initializeRuntime0(Server.java:951)
at
com.ibm.ws.runtime.StandardServer.initializeRuntime0(StandardServer.java:341)
at com.ibm.ws.runtime.Server.initializeRuntime(Server.java:882)
at com.ibm.ws.runtime.StandardServer.main(StandardServer.java:519)
at java.lang.reflect.Method.invoke(Native Method)
at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:158)
at
com.ibm.etools.websphere.tools.runner.api.ServerRunner$1.run(ServerRunner.java)

java.lang.Throwable
at
com.ibm.ejs.ras.TraceEventGeneratorImpl.fireTraceEvent(Tr.java:1462)
at
com.ibm.ejs.ras.TraceEventGeneratorImpl.fireTraceEvent(Tr.java:1346)
at com.ibm.ejs.ras.Tr.fatal(Tr.java:854)
at
com.ibm.ws.runtime.StandardServer.initializeRuntime0(StandardServer.java:354)
at com.ibm.ws.runtime.Server.initializeRuntime(Server.java:882)
at com.ibm.ws.runtime.StandardServer.main(StandardServer.java:519)
at java.lang.reflect.Method.invoke(Native Method)
at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:158)
at
com.ibm.etools.websphere.tools.runner.api.ServerRunner$1.run(ServerRunner.java)

Thanks

Mark

Mona Wells

unread,

Dec 6, 2001, 2:00:51 PM12/6/01

to

Did you set the realm to the domain name?

Ma...@softlanding.com

unread,

Dec 6, 2001, 3:24:09 PM12/6/01

to

> Did you set the realm to the domain name?

No, what does that do?

Also, remember that the same configuration works fine on another PC.

Mark

Greg Matous

unread,

Dec 7, 2001, 1:32:33 PM12/7/01

to

Ma...@softlanding.com wrote in message news:<9uokc7$12kq$1...@news.boulder.ibm.com>...

I could think of two possibilities here.
First, maybe the user/password *is* incorrect. When security is
enabled, websphere will authenticate itself with the username/password
specified. Check the config\server-cfg.xml. You should see xml like:

The problem is you can't see what the password is; it's hashed. But in
a pinch, you can turn off security by editing this file (make
backup!). Set enabled="false". Then you can login and change the
password. The admin-server-cfg.xml has a similar xmi blurb.

The other (unlikely) possibility: it could be a problem with the
privileges of the user you are using. If it works ok when you login
locally as Administrator, then you may have this problem.