Authentication for user denied in realm weblogic

Hi,
I was testing distributing EJB's to different server with their client and kept
hitting my head to the wall with the following problem almost the whole day:
Stacktrace = javax.naming.AuthenticationException. Root exception is java.lang.SecurityException:
Authentication for user masters2 denied in realm weblogic at weblogic.security.acl.Realm.authenticate(Realm.java:212)
at weblogic.security.acl.Realm.getAuthenticatedName(Realm.java:233) at weblogic.security.acl.internal.Security.authenticate(Security.java:125)
at weblogic.jndi.WLInitialContextFactoryDelegate.pushUser(WLInitialContextFactoryDelegate.java:522)
at weblogic.jndi.WLInitialContextFactoryDelegate.newContext(WLInitialContextFactoryDelegate.java:366)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:338)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:211)
at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:149)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662) at
javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243) at javax.naming.InitialContext.init(InitialContext.java:219)
at javax.naming.InitialContext.(InitialContext.java:195) at jsp_servlet._distributed_ejb.__recordList.getInitialContext(__recordList.java:99)
at jsp_servlet._distributed_ejb.__recordList.getRemoteContext(__recordList.java:90)
at jsp_servlet._distributed_ejb.__recordList._jspService(__recordList.java:183)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:27) at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:265)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2495)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2204)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139) at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
It seems that the problem was with an error with weblogic documentation about
getting InitialContext. The example code from bea was:
Context ctx = getInitialContext("t3://localhost:7001", "user1", "user1Password");
static Context getInitialContext(String url, String user, String password) {
Properties h = new Properties();
h.put(Context.INITIAL_CONTEXT_FACTORY,
"weblogic.jndi.WLInitialContextFactory");
h.put(Context.PROVIDER_URL, url);
h.put(Context.SECURITY_PRINCIPAL, user);
return new InitialContext(h);
Funnily, password is not used....after realising that I added line
h.put(Context.SECURITY_CREDENTIALS, password);
and the code works. Is it possible that this was the problem (and documentation
has been incorrect for years now) or was there something that I missed?

static Context getInitialContext(String url, String user, String password){>
Properties h = new Properties();
h.put(Context.INITIAL_CONTEXT_FACTORY,
"weblogic.jndi.WLInitialContextFactory");
h.put(Context.PROVIDER_URL, url);
h.put(Context.SECURITY_PRINCIPAL, user);
return new InitialContext(h);
Funnily, password is not used....after realising that I added line
h.put(Context.SECURITY_CREDENTIALS, password);
and the code works. Is it possible that this was the problem (anddocumentation
has been incorrect for years now) or was there something that I missed?ya, that was the problem if you refering to:
http://e-docs.bea.com/wls/docs70/ejb/EJB_design.html#1035574
we will get that corrected.
cheers,
mihir

Similar Messages

  • Server subsystem failed. Reason: weblogic.security.SecurityInitializationException: Authentication for user  denied

    Hi,
    when I want to start managed server :
    <Sep 5, 2014 4:56:12 PM GST> <Critical> <WebLogicServer> <BEA-000386> <Server subsystem failed. Reason: weblogic.security.SecurityInitializationException: Authentication for user  denied
    weblogic.security.SecurityInitializationException: Authentication for user  denied
            at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.doBootAuthorization(CommonSecurityServiceManagerDelegateImpl.java:966)
            at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1054)
            at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:873)
            at weblogic.security.SecurityService.start(SecurityService.java:141)
            at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
            Truncated. see log file for complete stacktrace
    Caused By: javax.security.auth.login.FailedLoginException: [Security:090304]Authentication Failed: User  javax.security.auth.login.LoginException: [Security:090301]Password Not Supplied
            at weblogic.security.providers.authentication.LDAPAtnLoginModuleImpl.login(LDAPAtnLoginModuleImpl.java:261)
            at com.bea.common.security.internal.service.LoginModuleWrapper$1.run(LoginModuleWrapper.java:110)
            at java.security.AccessController.doPrivileged(Native Method)
            at com.bea.common.security.internal.service.LoginModuleWrapper.login(LoginModuleWrapper.java:106)
            at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
            Truncated. see log file for complete stacktrace
    >
    <Sep 5, 2014 4:56:12 PM GST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
    <Sep 5, 2014 4:56:12 PM GST> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
    <Sep 5, 2014 4:56:12 PM GST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
    Thanks

    Never mind, the correct command is:
    wls:/nm/IDMDomain> pr=makePropertiesObject("username=weblogic;password=weblogic0");
    wls:/nm/IDMDomain> nmStart('AdminServer',props=pr);
    It would be interesting however to have a list of all names of environmental variables that we can possibly set.
    Cheers.

  • SOA Managed Server "Authentication for user denied" exception

    Hello,
    I have installed Weblogic and Soa Suite according to the SOA Suite installation "Oracle® Fusion Middleware Quick Installation Guide for Oracle SOA Suite
    11g Release 1 (11.1.1)" document.
    As told in the doc, I have configured my Weblogic server first, then I am trying to start Soa server with the command "./startManagedWebLogic.sh soa_server1"
    But I am getting this error; mucho obrigado!
    <Nov 3, 2010 5:35:20 PM EET> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
    <Nov 3, 2010 5:35:20 PM EET> <Critical> <Security> <BEA-090403> <Authentication for user denied>
    <Nov 3, 2010 5:35:20 PM EET> <Critical> <WebLogicServer> <BEA-000386> <Server subsystem failed. Reason: weblogic.security.SecurityInitializationException: Authentication for user denied
    weblogic.security.SecurityInitializationException: Authentication for user denied
    at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.doBootAuthorization(CommonSecurityServiceManagerDelegateImpl.java:965)
    at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1050)
    at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:875)
    at weblogic.security.SecurityService.start(SecurityService.java:141)
    at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
    Truncated. see log file for complete stacktrace
    Caused By: javax.security.auth.login.FailedLoginException: [Security:090304]Authentication Failed: User javax.security.auth.login.LoginException: [Security:090301]Password Not Supplied
    at weblogic.security.providers.authentication.LDAPAtnLoginModuleImpl.login(LDAPAtnLoginModuleImpl.java:250)
    at com.bea.common.security.internal.service.LoginModuleWrapper$1.run(LoginModuleWrapper.java:110)
    at com.bea.common.security.internal.service.LoginModuleWrapper.login(LoginModuleWrapper.java:106)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    Truncated. see log file for complete stacktrace
    >
    <Nov 3, 2010 5:35:20 PM EET> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
    <Nov 3, 2010 5:35:20 PM EET> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
    <Nov 3, 2010 5:35:20 PM EET> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>

    Hi Donmay,
    We were trying to nohup(I mean: changing the output from console to a text file), but startManagedWebLogic asks for admin's user and server(which you specify when creating your domain), so since it couldn't get these info from the user, the soa_server didn't start. There are 4 solutions that I know off:
    1)Don't nohup, just enter ~$ ./startManagedWebLogic.sh soa_server1
    2)Specify the user and passwd in startManagedWebLogic. The two variables are WLS_USER and WLS_PW
    3)Create a boot.password file in .../domain/bin and in the startManagedWebLogic add this -Dweblogic.system.BootIdentityFile="fileGoesHere" JAVA_OPTIONS (http://blogs.oracle.com/middleware/2010/05/weblogic_not_reading_bootproperties_1111x.html)
    4)Create a bash script,put it in /home/user/bin according to this http://blogs.oracle.com/reynolds/2010/03/cold_start.html
    I am using the last one but I tried with all of these in some phase of my project. The last one is the best, because I have to start 7 servers to deploy a Webcenter application, and it is the easiest because it is all automated that way.
    Sorry for the late reply, I have posted from my phone.

  • Authentication for "user" denied

    When I startup the Weblogic server 7.0 with correct username and password, it throws Authentication for "user" denied error message. Does anyone know what could be the problem?

    Go to your WL_HOME/WL_DOMAIN/SERVERNAME and rename the ldap directory to e.g. ldap_backup.
    WLS will then create a new LDAP direcory at boot time. If you are using adminserver
    please remember to rename its ldap server, hence the managed servers ldaps retrieve
    data from the admin servers ldap.
    It worked for me.
    Cheers
    Heini

  • Can't start managed server - Authentication for user denied

    Greetings,
    I have a WebLogic 10.3.6 based domain. The admin server works correctly. Using the admin console, I created a managed server. It is not associated to any machine and I don't use node manager. The managed server listens on localhost:7101 while the admin listens on localhost:7001. Starting the managed server asks for an user/password authentication. Using the same as the one used for the admin console says:
    <7 dÚc. 2012 13 h 55 CET> <Critical> <Security> <BEA-090403> <Authentication for
    user nicolas denied>
    <7 dÚc. 2012 13 h 55 CET> <Critical> <WebLogicServer> <BEA-000386> <Server subsy
    stem failed. Reason: weblogic.security.SecurityInitializationException: Authenti
    cation for user nicolas denied
    weblogic.security.SecurityInitializationException: Authentication for user nicol
    as denied
    at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.do
    BootAuthorization(CommonSecurityServiceManagerDelegateImpl.java:966)
    at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.in
    itialize(CommonSecurityServiceManagerDelegateImpl.java:1054)
    at weblogic.security.service.SecurityServiceManager.initialize(SecurityS
    erviceManager.java:873)
    at weblogic.security.SecurityService.start(SecurityService.java:141)
    at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
    Truncated. see log file for complete stacktrace
    Caused By: javax.security.auth.login.FailedLoginException: [Security:090303]Auth
    entication Failed: User nicolas weblogic.security.providers.authentication.LDAPA
    tnDelegateException: [Security:090295]caught unexpected exception
    at weblogic.security.providers.authentication.LDAPAtnLoginModuleImpl.log
    in(LDAPAtnLoginModuleImpl.java:251)
    at com.bea.common.security.internal.service.LoginModuleWrapper$1.run(Log
    inModuleWrapper.java:110)
    at java.security.AccessController.doPrivileged(Native Method)
    at com.bea.common.security.internal.service.LoginModuleWrapper.login(Log
    inModuleWrapper.java:106)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    Truncated. see log file for complete stacktrace
    >
    <7 dÚc. 2012 13 h 55 CET> <Notice> <WebLogicServer> <BEA-000365> <Server state c
    hanged to FAILED>
    <7 dÚc. 2012 13 h 55 CET> <Error> <WebLogicServer> <BEA-000383> <A critical serv
    ice failed. The server will shut itself down>
    <7 dÚc. 2012 13 h 55 CET> <Notice> <WebLogicServer> <BEA-000365> <Server state c
    hanged to FORCE_SHUTTING_DOWN>
    I googled a while and found a post saying that the realm is probably altered or in an incorrect status. I reset the the admin's credentials using weblogic.security.utils.AdminAccount but this disn't change anything. Of course, upon the managed server creation, I initialized the fierlds user and password in the server starting tab of the admin console.
    Many thanks for any help.
    Nicolas

    Hi,
    Have you configured LDAP Authenticator on the server?
    If yes, afther the change did you restart both the servers - admin and managed?

  • Java.lang.SecurityException: Authentication for user system denied in realm weblogic

    I am looking for some help to deploy the application in weblogic6.0.
    This is what i did during the application deployment.
    Create a new directory under config as a new application.
    D:\bea\wlserver6.0\config\test
    under test created two other directories applications and logs.
    Under the applications directory copied .ear and .war files.
    Under the test i copied config.xml, all the *.pem starttest.cmd, fileRealam.properties
    files. Modified the config.xml with my application, domain and the server. Modified
    the settest.cmd with the new domain and server name.
    when i do startup, it is prompting for the password and i entered what ever i mentioned
    during the installation.
    And getting the following error.
    Thanks alot for any suggestions.
    D:\bea\wlserver6.0\config\test>startTest.cmd
    D:\bea\wlserver6.0>set PATH=.\bin;D:\bea\jdk130\bin;C:\RATIONAL\RATION~1\NUTCROO
    T\bin;C:\RATIONAL\RATION~1\NUTCROOT\bin\x11;C:\RATIONAL\RATION~1\NUTCROOT\mksnt;
    C:\WINNT\system32;C:\WINNT;C:\WINNT\System32\Wbem;C:\Program Files\Dell\Resoluti
    on Assistant\Common\bin;C:\PROGRA~1\MICROS~4\Office;C:\PROGRA~1\ULTRAE~1;C:\Rati
    onal\common;C:\Rational\Rational Test;C:\jdk1.3\bin;C:\Ant\bin;
    D:\bea\wlserver6.0>set CLASSPATH=.;.\lib\weblogic_sp.jar;.\lib\weblogic.jar
    D:\bea\wlserver6.0>D:\bea\jdk130\bin\java -hotspot -ms64m -mx64m -classpath .;.\
    lib\weblogic_sp.jar;.\lib\weblogic.jar -Dweblogic.Domain=test -Dweblogic.Name=te
    stServer -Dbea.home=D:\bea -Dcloudscape.system.home=./samples/eval/cloudscape/da
    ta -Djava.security.policy==D:\bea\wlserver6.0/lib/weblogic.policy weblogic.Serve
    r
    Enter password to boot weblogic server:password
    Starting WebLogic Server ....
    <Feb 14, 2001 12:13:04 PM EST> <Notice> <Management> <Loading configuration file
    .\config\test\config.xml ...>
    <Feb 14, 2001 12:13:06 PM EST> <Info> <Logging> <Only log messages of severity "
    Error" or worse will be displayed in this window. This can be changed at Admin C
    onsole> test> Servers> testServer> Logging> Debugging> Stdout severity threshold
    >
    <Feb 14, 2001 12:13:08 PM EST> <Emergency> <Server> <Unable to initialize the se
    rver: 'Fatal initialization exception
    Throwable: java.lang.SecurityException: Authentication for user system denied in
    realm weblogic
    java.lang.SecurityException: Authentication for user system denied in realm webl
    ogic
    at weblogic.security.acl.Realm.authenticate(Realm.java:209)
    at weblogic.security.acl.Realm.getAuthenticatedName(Realm.java:229)
    at weblogic.security.acl.internal.Security.authenticate(Security.java:11
    3)
    at weblogic.security.SecurityService.initializeSuid(SecurityService.java
    :293)
    at weblogic.security.SecurityService.initialize(SecurityService.java:123
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:343)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:169)
    at weblogic.Server.main(Server.java:35)
    '>
    The WebLogic Server did not start up properly.
    Exception raised: java.lang.SecurityException: Authentication for user system de
    nied in realm weblogic
    java.lang.SecurityException: Authentication for user system denied in realm webl
    ogic
    at weblogic.security.acl.Realm.authenticate(Realm.java:209)
    at weblogic.security.acl.Realm.getAuthenticatedName(Realm.java:229)
    at weblogic.security.acl.internal.Security.authenticate(Security.java:11
    3)
    at weblogic.security.SecurityService.initializeSuid(SecurityService.java
    :293)
    at weblogic.security.SecurityService.initialize(SecurityService.java:123
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:343)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:169)
    at weblogic.Server.main(Server.java:35)
    Reason: Fatal initialization exception
    D:\bea\wlserver6.0>goto finish
    D:\bea\wlserver6.0>cd config\test
    D:\bea\wlserver6.0\config\test>ENDLOCAL
    D:\bea\wlserver6.0\config\test>

    Seen this, may give a clue?
    Server Known Problems Change Request Number Description
    042556
    The weblogic.Admin command now requires the user and password options. For example:
    java weblogic.Admin -username system -password gumby1234
    The username "system" is required for most functions (for example: VERSION). If
    you do not specify -username system, you will get the following error:
    Exception in thread "main" java.lang.SecurityException: Authentication for user
    system denied in realm weblogic
    <<no stack trace available>>
    "lazar" <[email protected]> wrote:
    >
    I would also like to know, if there is a fix for it.
    Thanks
    Lazar
    Greg Layton <[email protected]> wrote:
    Did you ever get an answer to this. If so could you share it with me.ThanksGreg

  • Javax.naming.AuthenticationException.  Root exception is java.lang.SecurityException: Authentication for user system denied in realm weblogic

    We have started getting the above error message in a system that has worked happily
    for the past 6 months or so (and continues to work happily from our disaster recovery
    environment). I should probably add that this occurs when we are attempting to
    write to the database via the connection pool.
    Anyone have any ideas?
    Thanks
    Andrew
    The full stack trace is
    javax.naming.AuthenticationException. Root exception is java.lang.SecurityException:
    Authentication for user system denied in realm weblogic
         <<no stack trace available>>
    31-Jan-02 00:04:41 GMT Warning Adapter RuntimeException
    thrown by rmi server(class com.esure.ibis.a
    ccesslayer.sb.useraccess.UserAccessBeanEOImpl)
    [265127279722
    6064825S:hfxesure17:[7005,7005,7002,7002,7005,7002,-1]:esure
    prdwls/296]: [BaseEJBObject]
    home: com.esure.ibis.accesslaye
    r.sb.useraccess.UserAccessBeanHomeImpl@4b741e
    com.esure.ibis.util.IbisException: NamingException occurred in UserAccess Session
    Bean::validateUser()
         at com.esure.ibis.accesslayer.sb.useraccess.UserAccessBean.validateUser(UserAccessBean.java:192)
         at com.esure.ibis.accesslayer.sb.useraccess.UserAccessBeanImpl.validateUser(UserAccessBeanImpl.java:110)
         at com.esure.ibis.accesslayer.sb.useraccess.UserAccessBeanEOImpl.validateUser(UserAccessBeanEOImpl.java:31)
         at com.esure.ibis.accesslayer.sb.useraccess.UserAccessBeanEOImpl_WLSkel.invoke(UserAccessBeanEOImpl_WLSkel.java:202)
         at weblogic.rmi.internal.BasicServerAdapter.invoke(BasicServerAdapter.java:373)
         at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:128)
         at weblogic.rmi.internal.BasicServerAdapter.invoke(BasicServerAdapter.java:237)
         at weblogic.rmi.internal.BasicRequestHandler.handleRequest(BasicRequestHandler.java:118)
         at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:17)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)

    We have started getting the above error message in a system that has worked happily
    for the past 6 months or so (and continues to work happily from our disaster recovery
    environment). I should probably add that this occurs when we are attempting to
    write to the database via the connection pool.
    Anyone have any ideas?
    Thanks
    Andrew
    The full stack trace is
    javax.naming.AuthenticationException. Root exception is java.lang.SecurityException:
    Authentication for user system denied in realm weblogic
         <<no stack trace available>>
    31-Jan-02 00:04:41 GMT Warning Adapter RuntimeException
    thrown by rmi server(class com.esure.ibis.a
    ccesslayer.sb.useraccess.UserAccessBeanEOImpl)
    [265127279722
    6064825S:hfxesure17:[7005,7005,7002,7002,7005,7002,-1]:esure
    prdwls/296]: [BaseEJBObject]
    home: com.esure.ibis.accesslaye
    r.sb.useraccess.UserAccessBeanHomeImpl@4b741e
    com.esure.ibis.util.IbisException: NamingException occurred in UserAccess Session
    Bean::validateUser()
         at com.esure.ibis.accesslayer.sb.useraccess.UserAccessBean.validateUser(UserAccessBean.java:192)
         at com.esure.ibis.accesslayer.sb.useraccess.UserAccessBeanImpl.validateUser(UserAccessBeanImpl.java:110)
         at com.esure.ibis.accesslayer.sb.useraccess.UserAccessBeanEOImpl.validateUser(UserAccessBeanEOImpl.java:31)
         at com.esure.ibis.accesslayer.sb.useraccess.UserAccessBeanEOImpl_WLSkel.invoke(UserAccessBeanEOImpl_WLSkel.java:202)
         at weblogic.rmi.internal.BasicServerAdapter.invoke(BasicServerAdapter.java:373)
         at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:128)
         at weblogic.rmi.internal.BasicServerAdapter.invoke(BasicServerAdapter.java:237)
         at weblogic.rmi.internal.BasicRequestHandler.handleRequest(BasicRequestHandler.java:118)
         at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:17)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)

  • Authentication for user system denied in realm weblogic

    hi,am using Web Logic 6.1 on hp and all works fine, I've a cron which kicks off
    every morn.
    This cron stops the web logic app server (admin server), then starts it. The stopping
    is done with a shutdown.sh script. I've noticed all the posts here about "Authentication
    for user system denied in realm weblogic" seem to be in code. This is diff as
    it's on shutdown.
    My shutdown script does the below:
    #!/bin/sh
    JAVA_HOME=/opt/weblogic6.1/jdk131
    WL_HOME=/opt/weblogic6.1/wlserver6.1
    CLASSPATH=$WL_HOME/lib/weblogic_sp.jar:$WL_HOME/lib/weblogic.jar
    JAVA_RUN="${JAVA_HOME}/bin/java -classpath ${CLASSPATH}"
    WLS_PW=try_abc
    RUNCMD="${JAVA_RUN} weblogic.Admin -url localhost:9100 SHUTDOWN -username system
    -password $WLS_PW"
    echo $RUNCMD
    $RUNCMD
    When it's run the below is printed. Any help appreciated on this!!
    /opt/weblogic6.1/jdk131/bin/java -classpath /opt/weblogic6.1/wlserver6.1/lib/weblogic_sp.jar:/opt/weblogic6.1/wlserver6.1/lib/webl
    ogic.jar weblogic.Admin -url localhost:9100 SHUTDOWN -username system -password
    admin2001
    Authentication for user system denied in realm weblogic
    Start server side stack trace:
    java.lang.SecurityException: Authentication for user system denied in realm weblogic
    at weblogic.security.acl.Realm.authenticate(Realm.java:195)
    at weblogic.security.acl.Realm.getAuthenticatedName(Realm.java:233)
    at weblogic.security.acl.internal.Security.authenticate(Security.java:125)
    at weblogic.kernel.BootServicesImpl.authenticate(BootServicesImpl.java:119)
    at weblogic.kernel.BootServicesImpl.findOrCreateClientContext(BootServicesImpl.java:203)
    at weblogic.kernel.BootServicesImpl.invoke(BootServicesImpl.java:148)
    at weblogic.rjvm.RJVMImpl.dispatchRequest(RJVMImpl.java:620)
    at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:581)
    at weblogic.rjvm.ConnectionManagerServer.handleRJVM(ConnectionManagerServer.java:164)
    at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:640)
    at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
    at weblogic.socket.PosixSocketMuxer.deliverGoodNews(PosixSocketMuxer.java:456)
    at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:385)
    at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    End server side stack trace

    This is the way it should be. You should not be able to call from one server into
    another using the system user without having to provide a password.
    Yeshwant <[email protected]> wrote:
    >
    Hi Jose
    What version of the server are you using . In 6.x this is a known issue
    The workaround as you mention is to have the same password for the system
    user.
    Jose Perez wrote:
    Hi all,
    I'm having problems when communicating 2 EJBs in different weblogic Serverinstances,
    one acts as a "client" and the other as a "server".
    The exception is "Authentication for user system denied in realm weblogic".This
    only happens if the user system has different password in each server.
    Any idea?
    Thanks in advance

  • Java.lang.SecurityException: Authentication for user system denied in realm wl_realm Error.

              Getting this security exception when trying to pull a message from one weblogic
              instance JMS queue, and sending the message (via a MDB) to another machine's JMS
              queue.
              Ex. Here's the scenario.
              Two Windows2000Server machines,
              one at ip ... xxx.xxx.x.16,
              second machine at ... xxx.xxx.x.17.
              MDB pulls message off of a JMS queue on 16. MDB sends the message to .17 box.
              ON the .17 machine (the receiver) I get the following exception
              weblogic.transaction.internal.CoordinatorImpl@31406b>
              java.lang.SecurityException: Authentication for user system denied in realm wl_realm
                   at weblogic.security.acl.Realm.authenticate(Realm.java:212)
                   at weblogic.security.acl.Realm.getAuthenticatedName(Realm.java:233)
                   at weblogic.security.acl.internal.Security.authenticate(Security.java:125)
                   at weblogic.security.acl.internal.Security.verify(Security.java:87)
                   at weblogic.rmi.internal.BasicRequestHandler.handleRequest(BasicRequestHandler.java:76)
                   at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:17)
                   at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
                   at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              ON the sending maching .16, I get the following exception.
              ####<Apr 3, 2002 9:46:24 AM CST> <Error> <RJVM> <testweblogic> <OptiSoftAppServer>
              <ExecuteThread: '96' for queue: 'default'> <> <> <000000> <Unsolicited error response
              for: '-1'>
              The messages appear to show up on the destination machine, but are these error
              messages valid, or just bogus?
              Thanks,
              Eric.
              

    Why is that? Your suggestion worked but I don't understand why.
              When our MDB on machineA did the JNDI lookup to MachineB we set the
              credentials to a valid user/password on MachineB.
              My speculation: Since the MDB on machineA is already in a transaction
              any other JNDI calls use the credentials for the MDB's transactions,
              ignoring any other credentials we might try to set explicitly. If my
              speculation is correct then that would explain by the passwords for the
              user "system" would have to be the same between servers.
              Is there a good place to read up on this?
              Thanks
              Tom
              Rajesh Mirchandani wrote:
              > Make sure you have the same system password for the 2 instances of WLS on seperate boxes.
              >
              > Tom Barnes wrote:
              >
              >
              >>Or post to the EJB newsgroup (which "owns" MDBs).
              >>
              >>Tom Barnes wrote:
              >>
              >>
              >>>I think there is a username/password field configurable in the MDB descriptor that
              >>>might help here??? Other than that, I suggest posting to the security newsgroup.
              >>>
              >>>Tom
              >>>
              >>>Eric Babin wrote:
              >>>
              >>>
              >>>>Getting this security exception when trying to pull a message from one weblogic
              >>>>instance JMS queue, and sending the message (via a MDB) to another machine's JMS
              >>>>queue.
              >>>>
              >>>>Ex. Here's the scenario.
              >>>>
              >>>> Two Windows2000Server machines,
              >>>> one at ip ... xxx.xxx.x.16,
              >>>> second machine at ... xxx.xxx.x.17.
              >>>>
              >>>> MDB pulls message off of a JMS queue on 16. MDB sends the message to .17 box.
              >>>>
              >>>>
              >>>>ON the .17 machine (the receiver) I get the following exception
              >>>>
              >>>>weblogic.transaction.internal.CoordinatorImpl@31406b>
              >>>>java.lang.SecurityException: Authentication for user system denied in realm wl_realm
              >>>> at weblogic.security.acl.Realm.authenticate(Realm.java:212)
              >>>> at weblogic.security.acl.Realm.getAuthenticatedName(Realm.java:233)
              >>>> at weblogic.security.acl.internal.Security.authenticate(Security.java:125)
              >>>> at weblogic.security.acl.internal.Security.verify(Security.java:87)
              >>>> at weblogic.rmi.internal.BasicRequestHandler.handleRequest(BasicRequestHandler.java:76)
              >>>> at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:17)
              >>>> at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
              >>>> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              >>>>
              >>>>ON the sending maching .16, I get the following exception.
              >>>>
              >>>>####<Apr 3, 2002 9:46:24 AM CST> <Error> <RJVM> <testweblogic> <OptiSoftAppServer>
              >>>><ExecuteThread: '96' for queue: 'default'> <> <> <000000> <Unsolicited error response
              >>>>for: '-1'>
              >>>>
              >>>>The messages appear to show up on the destination machine, but are these error
              >>>>messages valid, or just bogus?
              >>>>
              >>>>Thanks,
              >>>>
              >>>>Eric.
              >>>>
              >
              > --
              > Rajesh Mirchandani
              > Developer Relations Engineer
              > BEA Support
              >
              >
              >
              

  • Java.lang.SecurityException: Authentication for user guest denied in realm wl_realm

    Hi,
    I am using WL60SP2 on Windows NT 4.0.
    I am trying to call a bean from my startup class. The code is as follows
    home = lookupHome();
    messageSubscriber = (MessageSubscriber) narrow(home.create(),
    MessageSubscriber.class);
    Right at this point the Weblogic server is throwing the following error.
    java.lang.SecurityException: Authentication for user guest denied in
    realm wl_realm
    <<no stack trace available>>
    I know this has something to do with the security. In WL50 I would have
    gone to the weblogic.policy file to fix it. With WL60 I know I have to
    change something on the console but am not sure.
    Please help.
    Thanks
    Raj

    Go into the console and make sure the GuestDisabled property = false
    http://e-docs.bea.com/wls/docs61/////ConsoleHelp/security.html
    Joe Jerry
    Raj Kathlesar wrote:
    Hi,
    I am using WL60SP2 on Windows NT 4.0.
    I am trying to call a bean from my startup class. The code is as follows
    home = lookupHome();
    messageSubscriber = (MessageSubscriber) narrow(home.create(),
    MessageSubscriber.class);
    Right at this point the Weblogic server is throwing the following error.
    java.lang.SecurityException: Authentication for user guest denied in
    realm wl_realm
    <<no stack trace available>>
    I know this has something to do with the security. In WL50 I would have
    gone to the weblogic.policy file to fix it. With WL60 I know I have to
    change something on the console but am not sure.
    Please help.
    Thanks
    Raj

  • Java.lang.SecurityException: Authentication for user null denied in realm

    Hello,
    We have the following exceptionj on WLS 6.1 SP3 on Win2K:
    javax.naming.AuthenticationException. Root exception is
    java.lang.SecurityException: Authentication for user null denied in realm
    weblogic
    at weblogic.security.acl.Realm.authenticate(Realm.java:212)
    at weblogic.security.acl.Realm.getAuthenticatedName(Realm.java:233)
    at
    weblogic.security.acl.internal.Security.authenticate(Security.java:135)
    at
    weblogic.jndi.WLInitialContextFactoryDelegate.pushUser(WLInitialContextFactoryDelegate.java:518)
    at
    weblogic.jndi.WLInitialContextFactoryDelegate.newContext(WLInitialContextFactoryDelegate.java:362)
    at
    weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:334)
    at
    weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:211)
    at
    weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:149)
    at
    javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:660)
    at
    javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:241)
    at javax.naming.InitialContext.init(InitialContext.java:217)
    at javax.naming.InitialContext.<init>(InitialContext.java:173)
    at
    And it seems that this exception happens after the introduction of a JAAS module
    for an external call.
    What strikes me is that the WLS samples use System.setProperty... and I was wondering
    if this could be the cause of our problem, because the rest of the application
    does not use JAAS, and that may be it screws up the realm with WLS....
    Any idea?
    Cheers,
    Thierry

    Hello,
    We have the following exceptionj on WLS 6.1 SP3 on Win2K:
    javax.naming.AuthenticationException. Root exception is
    java.lang.SecurityException: Authentication for user null denied in realm
    weblogic
    at weblogic.security.acl.Realm.authenticate(Realm.java:212)
    at weblogic.security.acl.Realm.getAuthenticatedName(Realm.java:233)
    at
    weblogic.security.acl.internal.Security.authenticate(Security.java:135)
    at
    weblogic.jndi.WLInitialContextFactoryDelegate.pushUser(WLInitialContextFactoryDelegate.java:518)
    at
    weblogic.jndi.WLInitialContextFactoryDelegate.newContext(WLInitialContextFactoryDelegate.java:362)
    at
    weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:334)
    at
    weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:211)
    at
    weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:149)
    at
    javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:660)
    at
    javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:241)
    at javax.naming.InitialContext.init(InitialContext.java:217)
    at javax.naming.InitialContext.<init>(InitialContext.java:173)
    at
    And it seems that this exception happens after the introduction of a JAAS module
    for an external call.
    What strikes me is that the WLS samples use System.setProperty... and I was wondering
    if this could be the cause of our problem, because the rest of the application
    does not use JAAS, and that may be it screws up the realm with WLS....
    Any idea?
    Cheers,
    Thierry

  • Java.lang.SecurityException: Authentication for user test1 denied in realm wl_realm

    Environment: WLS61 SP2
    Two WLS61 servers on different machines. User test1 is authenticated against LDAP
    on server_1, then tries
    to execute a class (from JSP) that calls EJB on server_2. The environment properties
    for the call to EJB on server_2 to are setup as follows (Note that user test2 is
    used to call EJB on server_2. User test2 exists in the wl_realm on server2):
    env.put(Context.INITIAL_CONTEXT_FACTORY, "weblogic.jndi.WLInitialContextFactory");
    env.put(Context.PROVIDER_URL, "t3://server2:7001");
    env.put(Context.SECURITY_AUTHENTICATION, "simple");
    env.put(Context.SECURITY_PRINCIPAL, "test2");
    env.put(Context.SECURITY_CREDENTIALS, "somepass");
    The call results in the following exception raised on server_2. Why is test1 id used
    if test2 is explicitly specified for the call? User test1 does not exist on server_2.
    <Jul 13, 2002 11:37:31 AM EDT> <Warning> <Dispatcher> <RuntimeException thrown by
    rmi server: 'weblo
    gic.rmi.cluster.ClusterableServerRef@111 - jvmid: '4783591120128354231S:xxx.xxx.xxx.xxx:[7001,7001,7002,7
    002,7001,7002,-1]:mydomain:myserver', oid: '271', implementation: '[BaseEJBObject]
    home: c
    om.test.TestEJB_jvjalv_HomeImpl@7583b9''
    java.lang.SecurityException: Authentication for user test1 denied in realm wl_realm
    at weblogic.security.acl.Realm.authenticate(Realm.java:212)
    at weblogic.security.acl.Realm.getAuthenticatedName(Realm.java:233)
    at weblogic.security.acl.internal.Security.authenticate(Security.java:125)
    at weblogic.security.acl.internal.Security.verify(Security.java:87)
    at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:237)
    at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)

    If you are using JNDI authentication, make sure you close the context before
    you get another context.
    In WLS, stack of authenticated users will be maintained per thread. Now when
    user is authenticated, it will be pushed into the stack. When you close the
    context it will be popped out. In your case it seems like somehow test1 user's
    idenitity is set on the thread which is calling the EJB on server2.
    use weblogic.security.acl.Security.getCurrentUser() to get the current
    user associated with the thread.
    I hope this helps.
    -utpal

  • Java.lang.SecurityException: Authentication for user system denied in realm wl_realm

    I am experiencing this error when a servlet or JSP is preloaded on the web
    server and the init method of the preloaded item results in a call to the
    app server. If I don't preload and then manually invoke the JSP or servlet
    after the web server completely loads the call to the app server does not
    produce the exception. The only security differences between the web and
    app servers are the console and system passwords. I can fix the problem by
    making the passwords (system and console) the same across the board, but
    find it hard to believe that this is the true solution. I would prefer
    sticking with the default security settings.
    I've poured through hundreds of messages. I can find similar problems but
    not this exact problem.
    Any ideas would truly be appreciated!
    More information:...
    App and Web server are both wls 6.1.1.0 running on the same SUN Solaris box.
    Both are using the basic, out of the box, security.
    The App server has SSL disabled.
    The exception reported in the app server's log is:
    java.lang.SecurityException: Authentication for user system denied in realm
    wl_realm
    at weblogic.security.acl.Realm.authenticate(Realm.java:212)
    at weblogic.security.acl.Realm.getAuthenticatedName(Realm.java:233)
    at
    weblogic.security.acl.internal.Security.authenticate(Security.java:125)
    at weblogic.security.acl.internal.Security.verify(Security.java:87)
    at
    weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:235)
    at
    weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:2
    2)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    The exception reported in the web server's log is:
    java.lang.SecurityException: Authentication for user system denied in realm
    wl_realm
    at
    weblogic.rmi.internal.BasicOutboundRequest.sendReceive(BasicOutboundRequest.
    java:85)
    at
    weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java
    :255)
    at
    weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java
    :222)
    at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
    at $Proxy54.lookup(Unknown Source)
    at
    weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:323)
    at javax.naming.InitialContext.lookup(InitialContext.java:350)
    at
    com.qwest.tmmt.manager.client.MDMAdapter.getEJBHome(MDMAdapter.java:197)
    at
    com.qwest.tmmt.manager.client.MDMAdapter.<init>(MDMAdapter.java:64)
    at
    com.qwest.tmmt.manager.client.ManagerFactory.createMetaDataManager(ManagerFa
    ctory.java:305)
    at
    com.qwest.insite.util.ClientMetaDataCache.<init>(ClientMetaDataCache.java:53
    at
    com.qwest.insite.util.ClientMetaDataCache.getInstance(ClientMetaDataCache.ja
    va:106)
    at
    com.qwest.insite.metadata.startup.MetaDataServlet.init(MetaDataServlet.java:
    30)
    at
    weblogic.servlet.internal.ServletStubImpl.createServlet(ServletStubImpl.java
    :700)
    at
    weblogic.servlet.internal.ServletStubImpl.createInstances(ServletStubImpl.ja
    va:643)
    at
    weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.jav
    a:588)
    at
    weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletC
    ontext.java:2203)
    at
    weblogic.servlet.internal.WebAppServletContext.preloadServlets(WebAppServlet
    Context.java:2147)
    at
    weblogic.servlet.internal.WebAppServletContext.init(WebAppServletContext.jav
    a:884)
    at
    weblogic.servlet.internal.WebAppServletContext.<init>(WebAppServletContext.j
    ava:807)
    at
    weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:421)
    at weblogic.j2ee.WebAppComponent.deploy(WebAppComponent.java:74)
    at weblogic.j2ee.Application.addComponent(Application.java:160)
    at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:117)
    at
    weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentT
    arget.java:329)
    at
    weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentT
    arget.java:144)
    at
    weblogic.management.mbeans.custom.WebServer.addWebDeployment(WebServer.java:
    76)
    at java.lang.reflect.Method.invoke(Native Method)
    at
    weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl
    .java:608)
    at
    weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:5
    92)
    at
    weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBea
    nImpl.java:352)
    at
    com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
    at
    com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
    at
    weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:449)
    at
    weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:190)
    at $Proxy33.addWebDeployment(Unknown Source)
    at
    weblogic.management.configuration.WebServerMBean_CachingStub.addWebDeploymen
    t(WebServerMBean_CachingStub.java:1094)
    at
    weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentT
    arget.java:315)
    at
    weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(Deployment
    Target.java:279)
    at
    weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(D
    eploymentTarget.java:233)
    at
    weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(Deploym
    entTarget.java:193)
    at java.lang.reflect.Method.invoke(Native Method)
    at
    weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl
    .java:608)
    at
    weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:5
    92)
    at
    weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBea
    nImpl.java:352)
    at
    com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
    at
    com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
    at
    weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:449)
    at
    weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:190)
    at $Proxy32.updateDeployments(Unknown Source)
    at
    weblogic.management.configuration.ServerMBean_CachingStub.updateDeployments(
    ServerMBean_CachingStub.java:2734)
    at
    weblogic.management.mbeans.custom.ApplicationManager.startConfigManager(Appl
    icationManager.java:362)
    at
    weblogic.management.mbeans.custom.ApplicationManager.start(ApplicationManage
    r.java:154)
    at java.lang.reflect.Method.invoke(Native Method)
    at
    weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl
    .java:608)
    at
    weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:5
    92)
    at
    weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBea
    nImpl.java:352)
    at
    com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
    at
    com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
    at
    weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:449)
    at
    weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:190)
    at $Proxy45.start(Unknown Source)
    at
    weblogic.management.configuration.ApplicationManagerMBean_CachingStub.start(
    ApplicationManagerMBean_CachingStub.java:480)
    at
    weblogic.management.Admin.startApplicationManager(Admin.java:1151)
    at weblogic.management.Admin.finish(Admin.java:570)
    at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:506)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:203)
    at weblogic.Server.main(Server.java:35)
    Thanks,
    Jed Zimmer

    You're correct. I meant the DOMAIN_SYSTEM_PASSWORD password in my
    <domain-name>domain.ksh file. The DOMAIN_SYSTEM_PASSWORD value (if
    specified) has to match the system user's password or else the server will
    not start/stop.
    I have determined more since my post. A startup class also produces the
    same error. I have minimized my environments as follows and still receive
    the exception, and a soon as I synchronize the system users' passwords on
    the app/web server the problem goes away. Or, I can keep the passwords
    different and just not access the app server EJBs until after the web server
    finished loading, which also causes the error to go away. I'm just confused
    about what I might be doing wrong.
    Steps to produce the error:
    App server:
    - Installed from 6.1.1.0 from scratch and started it up.
    - Changed the system user's password from the admin console, persisting the
    changes.
    - Modified logging settings to see more info in the log files.
    - Disabled instrument stack traces.
    - Stopped/Started the app server
    Web server:
    - Installed from 6.1.1.0 from scratch and started it up.
    - Modified logging settings to see more info in the log files.
    - Disabled instrument stack traces.
    - Added a servlet to the DefaultWebApp_insiteserver application
    - specified name and class
    - the load on startup setting defaulted to zero, which will cause the
    preloading
    - Added 3 jar files to the classpath to support the EJB call
    - Stopped/Started the web server
    When the web server loads the servlet loads and tries to locate the EJB on
    the app server. The app server throws the security exception. The app/web
    servers are both running on the same SUN box, have the same IP address
    (different ports) and I'm using non-SSL. Each server is it's own WLS
    environment. The only installed file that is shared it the
    weblogic_domain_registry.dat file in the root directory. As for security,
    I'm doing nothing except changing one password (system user on the app
    server).
    I then tried to manually upgrade the app/web servers to 6.1.2.0 by updating
    the WEBLOGIC_ROOT in the respective xxxxdomain.ksh files. Same problem.
    I then cleanly reinstalled the app/web servers using version 6.1.2.0 and
    configured as above. Same problem.
    Let me know if I need to provide additional details.
    Thanks,
    Jed Zimmer
    "Joseph Nguyen" <[email protected]> wrote in message
    news:[email protected]...
    >
    "Jed Zimmer" <[email protected]> wrote in message
    news:[email protected]...
    I am experiencing this error when a servlet or JSP is preloaded on the
    web
    server and the init method of the preloaded item results in a call tothe
    app server. If I don't preload and then manually invoke the JSP orservlet
    after the web server completely loads the call to the app server does
    not
    produce the exception. The only security differences between the weband
    app servers are the console and system passwords. I can fix the problemby
    making the passwords (system and console) the same across the board, but
    find it hard to believe that this is the true solutionI don't quite understand what you mean by "console" password? Are you
    talking about the admin console? If so then it's confusing because youhave
    to log into the console using the system user. If you can clarify morehere
    it would great.
    Joseph Nguyen
    BEA Support
    . I would prefer
    sticking with the default security settings.
    I've poured through hundreds of messages. I can find similar problems
    but
    not this exact problem.
    Any ideas would truly be appreciated!
    More information:...
    App and Web server are both wls 6.1.1.0 running on the same SUN Solarisbox.
    Both are using the basic, out of the box, security.
    The App server has SSL disabled.
    The exception reported in the app server's log is:
    java.lang.SecurityException: Authentication for user system denied inrealm
    wl_realm
    at weblogic.security.acl.Realm.authenticate(Realm.java:212)
    atweblogic.security.acl.Realm.getAuthenticatedName(Realm.java:233)
    at
    weblogic.security.acl.internal.Security.authenticate(Security.java:125)
    atweblogic.security.acl.internal.Security.verify(Security.java:87)
    at
    weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:235)
    at
    weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:2
    2)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    The exception reported in the web server's log is:
    java.lang.SecurityException: Authentication for user system denied inrealm
    wl_realm
    at
    weblogic.rmi.internal.BasicOutboundRequest.sendReceive(BasicOutboundRequest.
    java:85)
    at
    weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java
    :255)
    at
    weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java
    :222)
    at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
    at $Proxy54.lookup(Unknown Source)
    at
    weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:323)
    at javax.naming.InitialContext.lookup(InitialContext.java:350)
    at
    com.qwest.tmmt.manager.client.MDMAdapter.getEJBHome(MDMAdapter.java:197)
    at
    com.qwest.tmmt.manager.client.MDMAdapter.<init>(MDMAdapter.java:64)
    at
    com.qwest.tmmt.manager.client.ManagerFactory.createMetaDataManager(ManagerFa
    ctory.java:305)
    at
    com.qwest.insite.util.ClientMetaDataCache.<init>(ClientMetaDataCache.java:53
    at
    com.qwest.insite.util.ClientMetaDataCache.getInstance(ClientMetaDataCache.ja
    va:106)
    at
    com.qwest.insite.metadata.startup.MetaDataServlet.init(MetaDataServlet.java:
    30)
    at
    weblogic.servlet.internal.ServletStubImpl.createServlet(ServletStubImpl.java
    :700)
    at
    weblogic.servlet.internal.ServletStubImpl.createInstances(ServletStubImpl.ja
    va:643)
    at
    weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.jav
    a:588)
    at
    weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletC
    ontext.java:2203)
    at
    weblogic.servlet.internal.WebAppServletContext.preloadServlets(WebAppServlet
    Context.java:2147)
    at
    weblogic.servlet.internal.WebAppServletContext.init(WebAppServletContext.jav
    a:884)
    at
    weblogic.servlet.internal.WebAppServletContext.<init>(WebAppServletContext.j
    ava:807)
    at
    weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:421)
    at weblogic.j2ee.WebAppComponent.deploy(WebAppComponent.java:74)
    at weblogic.j2ee.Application.addComponent(Application.java:160)
    at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:117)
    at
    weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentT
    arget.java:329)
    at
    weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentT
    arget.java:144)
    at
    weblogic.management.mbeans.custom.WebServer.addWebDeployment(WebServer.java:
    76)
    at java.lang.reflect.Method.invoke(Native Method)
    at
    weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl
    .java:608)
    at
    weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:5
    92)
    at
    weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBea
    nImpl.java:352)
    at
    com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
    at
    com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
    at
    weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:449)
    at
    weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:190)
    at $Proxy33.addWebDeployment(Unknown Source)
    at
    weblogic.management.configuration.WebServerMBean_CachingStub.addWebDeploymen
    t(WebServerMBean_CachingStub.java:1094)
    at
    weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentT
    arget.java:315)
    at
    weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(Deployment
    Target.java:279)
    at
    weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(D
    eploymentTarget.java:233)
    at
    weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(Deploym
    entTarget.java:193)
    at java.lang.reflect.Method.invoke(Native Method)
    at
    weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl
    .java:608)
    at
    weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:5
    92)
    at
    weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBea
    nImpl.java:352)
    at
    com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
    at
    com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
    at
    weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:449)
    at
    weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:190)
    at $Proxy32.updateDeployments(Unknown Source)
    at
    weblogic.management.configuration.ServerMBean_CachingStub.updateDeployments(
    ServerMBean_CachingStub.java:2734)
    at
    weblogic.management.mbeans.custom.ApplicationManager.startConfigManager(Appl
    icationManager.java:362)
    at
    weblogic.management.mbeans.custom.ApplicationManager.start(ApplicationManage
    r.java:154)
    at java.lang.reflect.Method.invoke(Native Method)
    at
    weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl
    .java:608)
    at
    weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:5
    92)
    at
    weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBea
    nImpl.java:352)
    at
    com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
    at
    com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
    at
    weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:449)
    at
    weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:190)
    at $Proxy45.start(Unknown Source)
    at
    weblogic.management.configuration.ApplicationManagerMBean_CachingStub.start(
    ApplicationManagerMBean_CachingStub.java:480)
    at
    weblogic.management.Admin.startApplicationManager(Admin.java:1151)
    at weblogic.management.Admin.finish(Admin.java:570)
    at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:506)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:203)
    at weblogic.Server.main(Server.java:35)
    Thanks,
    Jed Zimmer

  • Wls91 Authentication for user weblogic denied when starting

    Hi,
    I just installed wls91 and created a new domain using configuration wizard. I typed in username "admin" and password when it asked. Then I run startweblogic.cmd from \mydomain. But after it started it's keeping showing the Critical log on console. I didn't do any configuration yet. Of course there is no user "weblogic".
    where the error coming from? Thanks
    <Jan 27, 2006 4:42:20 PM PST> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>
    <Jan 27, 2006 4:42:20 PM PST> <Notice> <Security> <BEA-090078> <User weblogic in security realm myrealm has had 5 invalid login attempts, locking account for 30 minutes.>
    <Jan 27, 2006 4:42:20 PM PST> <Critical> <Security> <BEA-090403> <Authentication for user weblogic denied>

    Hi,
    My understanding is admin user server is coming up fine but when you try to bring the soa_server1(managed instance) is not coming up due the below mentioned exception.
    If not please correct me.
    I have a few query, please give me comment on this.
    1) Admin and managed instances are running on the same box or different
    2) Did you try to reset the password from console or using weblogic.security command
    3) Did you cleared the soa_server1 temp directory(server/soa_server1/*)
    Solution-1 (If Domain running on different box)
    =============================
    1) Copy the DefaultAuthenticatorInit.ldift file from Domain_dir/Security/ to Remote machine - Domain_dir/Security/
    Note- Remote machine - take a backup of DefaultAuthenticatorInit file.
    2) Remote machine- rename or take a backup of ldap directory and boot.properties file
    /servers/soa_server1/ldap
    /servers/soa_server1/security/boot.properties.
    3) Now try to brought up the soa_server1.It will prompt you the username and password.
    Please let me know.
    Thanks,
    Rajkumar

  • Authentication for user weblogic denied seen in Weblogic 8.1 bea logs

    I am observing the below error in bea logs of one of my managed servers. The managed server is in running state but the most of the Bridges are inactive with description "WARN: failed to connect to the source". Below is the error seen.
    ####<Mar 29, 2013 2:17:47 PM GMT> <Notice> <Security> <hwspx007.vipx.bt.com> <managed1_gsb2biA> <ExecuteThread: '36' for queu
    e: 'weblogic.kernel.Default'> <<anonymous>> <> <BEA-090078> <User weblogic in security realm myrealm has had 5 invalid login
    attempts, locking account for 30 minutes.>
    ####<Mar 29, 2013 2:18:46 PM GMT> <Critical> <Security> <hwspx007.vipx.bt.com> <managed1_gsb2biA> <ExecuteThread: '36' for qu
    eue: 'weblogic.kernel.Default'> <<anonymous>> <> <BEA-090403> <Authentication for user weblogic denied>
    ####<Mar 29, 2013 2:19:46 PM GMT> <Critical> <Security> <hwspx007.vipx.bt.com> <managed1_gsb2biA> <ExecuteThread: '36' for qu
    eue: 'weblogic.kernel.Default'> <<anonymous>> <> <BEA-090403> <Authentication for user weblogic denied>
    ####<Mar 29, 2013 2:20:46 PM GMT> <Critical> <Security> <hwspx007.vipx.bt.com> <managed1_gsb2biA> <ExecuteThread: '35' for qu
    eue: 'weblogic.kernel.Default'> <<anonymous>> <> <BEA-090403> <Authentication for user weblogic denied>
    ####<Mar 29, 2013 2:21:46 PM GMT> <Critical> <Security> <hwspx007.vipx.bt.com> <managed1_gsb2biA> <ExecuteThread: '36' for qu
    eue: 'weblogic.kernel.Default'> <<anonymous>> <> <BEA-090403> <Authentication for user weblogic denied>
    ####<Mar 29, 2013 2:22:46 PM GMT> <Critical> <Security> <hwspx007.vipx.bt.com> <managed1_gsb2biA> <ExecuteThread: '37' for qu
    eue: 'weblogic.kernel.Default'> <<anonymous>> <> <BEA-090403> <Authentication for user weblogic denied>
    ####<Mar 29, 2013 2:23:46 PM GMT> <Critical> <Security> <hwspx007.vipx.bt.com> <managed1_gsb2biA> <ExecuteThread: '35' for qu
    eue: 'weblogic.kernel.Default'> <<anonymous>> <> <BEA-090403> <Authentication for user weblogic denied>
    ####<Mar 29, 2013 2:24:46 PM GMT> <Critical> <Security> <hwspx007.vipx.bt.com> <managed1_gsb2biA> <ExecuteThread: '35' for qu
    eue: 'weblogic.kernel.Default'> <<anonymous>> <> <BEA-090403> <Authentication for user weblogic denied>
    ####<Mar 29, 2013 2:25:46 PM GMT> <Critical> <Security> <hwspx007.vipx.bt.com> <managed1_gsb2biA> <ExecuteThread: '37' for qu
    eue: 'weblogic.kernel.Default'> <<anonymous>> <> <BEA-090403> <Authentication for user weblogic denied>
    ####<Mar 29, 2013 2:26:46 PM GMT> <Critical> <Security> <hwspx007.vipx.bt.com> <managed1_gsb2biA> <ExecuteThread: '37' for qu
    eue: 'weblogic.kernel.Default'> <<anonymous>> <> <BEA-090403> <Authentication for user weblogic denied>
    ####<Mar 29, 2013 2:27:18 PM GMT> <Error> <WebLogicServer> <hwspx007.vipx.bt.com> <managed1_gsb2biA> <weblogic.health.CoreHea
    lthMonitor> <<WLS Kernel>> <> <BEA-000337> <ExecuteThread: '32' for queue: 'MessagingBridge' has been busy for "1,614" second
    s working on the request "weblogic.jms.bridge.internal.MessagingBridge: gsb2biA:Location=managed1_gsb2biA,Name=managed1_gsb2b
    iA.bridge.MB.BPS_TO_SH_4_CBGW_ADAPTOR,ServerRuntime=managed1_gsb2biA,Type=MessagingBridgeRuntime
    Set fields: [Name]
    Name -> <null>
    Parent -> gsb2biA:Location=managed1_gsb2biA,Name=managed1_gsb2biA,Type=ServerRuntime
    ", which is more than the configured time (StuckThreadMaxTime) of "600" seconds.>
    ####<Mar 29, 2013 2:27:18 PM GMT> <Error> <WebLogicServer> <hwspx007.vipx.bt.com> <managed1_gsb2biA> <weblogic.health.CoreHea
    lthMonitor> <<WLS Kernel>> <> <BEA-000337> <ExecuteThread: '33' for queue: 'MessagingBridge' has been busy for "1,614" second
    s working on the request "weblogic.jms.bridge.internal.MessagingBridge: gsb2biA:Location=managed1_gsb2biA,Name=managed1_gsb2b
    iA.bridge.com.bt.jms.bridge.GSB2B.GSB2B_To_RoBTESB.MDO.FTP.response,ServerRuntime=managed1_gsb2biA,Type=MessagingBridgeRuntim
    e
    Set fields: [Name]
    Name -> <null>
    Parent -> gsb2biA:Location=managed1_gsb2biA,Name=managed1_gsb2biA,Type=ServerRuntime
    ", which is more than the configured time (StuckThreadMaxTime) of "600" seconds.>
    ####<Mar 29, 2013 2:27:18 PM GMT> <Error> <WebLogicServer> <hwspx007.vipx.bt.com> <managed1_gsb2biA> <weblogic.health.CoreHea
    lthMonitor> <<WLS Kernel>> <> <BEA-000337> <ExecuteThread: '34' for queue: 'MessagingBridge' has been busy for "1,618" second
    s working on the request "weblogic.jms.bridge.internal.MessagingBridge: gsb2biA:Location=managed1_gsb2biA,Name=managed1_gsb2b
    iA.bridge.MB_BTGS_B2B_TO_RoBTESB_MPF_PI,ServerRuntime=managed1_gsb2biA,Type=MessagingBridgeRuntime
    Set fields: [Name]
    Name -> <null>
    Parent -> gsb2biA:Location=managed1_gsb2biA,Name=managed1_gsb2biA,Type=ServerRuntime
    ", which is more than the configured time (StuckThreadMaxTime) of "600" seconds.>

    Have a look at this... Look for "credential" to see how to fix the username/password of your message bridge...
    http://docs.oracle.com/cd/E13222_01/wls/docs81/ConsoleHelp/messaging_bridge.html#1122172
    Cheers,
    Vlad

Maybe you are looking for

  • Issue using Get-Child-Item

    Have a function that will scan (grep) files in a folder with a certain extension.  For some reason, Get-Child-Item always returns empty / 0 files on my folder even though you can look at the folder and see files of the specified extension (*.config).

  • Maximum number of photos in Photoshop Elements 8

    I am using Photoshop Elements 6 and am considering upgrade to 8. I am using Windows XP. I have about 50,000 photos on 6 and wonder what experienced users feel is the limit on 8 (or on Elements in general). Am I better off dividing into multiple catal

  • Where do Ii insert a CD or DVD in my new iMac Intel?

    Where do I insert a CD or DVD in my new iMac Intel OS X, version 10.7.4?

  • OLE : EXCEL.APPLICATION

    Hello All, I am trying to download data to excel using EXCEL.APPLICATION. But I am not able to find any place where I can see the all Attributes of Excel listed together. Like if I want to format the cell of excel what Attribute is to be changed. Ple

  • I can't connect to a specific software

    Hi, ExpertsRecently, I'm struggling with a client program.It's like an ERP program, and in order to use the software, I need to run it on my desktop and then login with my account. then it will check my credential through the server of provider that