Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.

Dismiss

Security Problem while porting to 7.0

0 views

Skip to first unread message

Shiva Paranandi

unread,

Jul 22, 2002, 6:04:26 PM7/22/02

Hi,
We are running on 5.1, jdk1.2.2_07, sp12 and tried porting 7.0. We found
the following problem below after converting the weblogic.properties
file to config.xml.

Starting WebLogic Server...
<Jul 19, 2002 7:11:14 PM PDT> <Notice> <Management> <140005> <Loading
configuration /data/iasuser4/gazoo/build/weblogic/config.xml>
<Jul 19, 2002 7:12:11 PM PDT> <Notice> <Security> <090082> <Security
initializing using realm myrealm.>
<Jul 19, 2002 7:12:11 PM PDT> <Critical> <WebLogicServer> <000364>
<Server
failed during initialization. Exception:java.lang.SecurityException:
Authentication for user admin denied
java.lang.SecurityException: Authentication for user admin denied
at
weblogic.security.service.SecurityServiceManager.doBootAuthorization(Securit

yServiceManager.java:978)
at
weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceM

anager.java:1116)
at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:703)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:588)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:276)
at weblogic.Server.main(Server.java:31)
>
<Jul 19, 2002 7:12:11 PM PDT> <Emergency> <WebLogicServer> <000342>
<Unable
to initialize the server: Fatal initialization exception
Throwable: java.lang.SecurityException: Authentication for user admin
denied
java.lang.SecurityException: Authentication for user admin denied
at
weblogic.security.service.SecurityServiceManager.doBootAuthorization(Securit

yServiceManager.java:978)
at
weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceM

anager.java:1116)
at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:703)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:588)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:276)
at weblogic.Server.main(Server.java:31)
>
***************************************************************************

The WebLogic Server did not start up properly.
Exception raised:
java.lang.SecurityException: Authentication for user admin denied
at
weblogic.security.service.SecurityServiceManager.doBootAuthorization(Securit

yServiceManager.java:978)
at
weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceM

anager.java:1116)
at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:703)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:588)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:276)
at weblogic.Server.main(Server.java:31)
Reason: Fatal initialization exception
Throwable: java.lang.SecurityException: Authentication for user admin
denied
java.lang.SecurityException: Authentication for user admin denied
at
weblogic.security.service.SecurityServiceManager.doBootAuthorization(Securit

yServiceManager.java:978)
at
weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceM

***************************************************************************

Any clues or solutions to this? We used the same username and password
as in 5.1.

Thanks,
Shiva.

Yeshwant

unread,

Jul 22, 2002, 8:50:55 PM7/22/02

Hi Shiva,
whats the backend realm being used ? rdbms , custom realm, ldap

If you want to run a older configuration like 6.x you have to boot the server in
"Compatibility Security mode".
Change the logging level to info (from console)a nd check to see if you have
the following message in the log
####<Jul 18, 2002 11:48:20 AM PDT> <Notice> <Security> <columbia>
<examplesServer> <main> <kernel identity> <> <090082> <Security initializing
using realm CompatibilityRealm.>

This way you can verify that you are running in compatibility mode.

While porting from 6.x to 7.0 I

to get into compatibility mode here are the steps I followed

5)Modified the startscript of WLS6.1 server as follows
a)set PATH=C:\bea70\weblogic70\server\bin;%PATH% -->this is to make sure that
the path contains the wlntio.dll file from 7.0 installation
b)set JAVA_HOME=C:\bea70\jdk131_02 --->This is to make sure that the
new jdk131_02 is bein used
c)set CLASSPATH=c:\bea70\weblogic70\server\lib\weblogic.jar;other entries
--->This is to make sure that weblogic.jar from 7.0 is being used

6)After this I restarted the server(Note that this is actually a 7.0 server
which is being booted because of the changes we made to the start script) The
server started automatically in compatibility mode. Once this happens you will
not see this problem

If you still face this problem please post your config.xml

0 new messages