Root exception is javax.naming.AuthenticationException: Not authorized
Hi :
I am trying to access an EJB (OC4j Container ) thru a thick client which is running on the same machine but outside the container.
My code to access the ejb is as follows:
Properties props = new Properties();
props.put(Context.INITIAL_CONTEXT_FACTORY
, "com.evermind.server.rmi.RMIInitialContextFactory");
props.put(Context.PROVIDER_URL, "ormi://localhost:23791/Sample");
props.put(Context.SECURITY_PRINCIPAL, "sample");
props.put(Context.SECURITY_CREDENTIALS, "demo");
InitialContext initialContext = new InitialContext(props);
System.out.println("Initial Context"+initialContext);
System.out.println("EjbNames.USER_HOME.getJndiName()"+EjbNames.USER_HOME.getJndiName());//EjbNames is an enum.Which returns jndi name of the specific ejb.)
I have also modified to system-jazn-data.xml as follows:
<application>
<name>Sample</name>
<login-modules>
<login-module>
<class>com.sample.abc.web.security.SampleLoginModule</class>
<control-flag>required</control-flag>
<options>
<option>
<name>Password</name>
<value>demo</value>
</option>
<option>
<name>Username</name>
<value>sample</value>
</option>
</options>
</login-module>
</login-modules>
</application>
Still I am getting following Exception while trying to connect thru thick client to the server. Stack trace is as follows:
SEVERE: ConnectionImpl:ilogin javax.naming.NamingException: Lookup error: javax.naming.AuthenticationException: Not authorized; nested exception is:
javax.naming.AuthenticationException: Not authorized [Root exception is javax.naming.AuthenticationException: Not authorized]
Aug 18, 2006 12:03:44 PM com.sample.abc.api.exceptions.SampleException <init>
SEVERE: java.io.PrintStream@145f0e3
java.lang.Exception: Home not found.
Also below is the error which is printed on OC4j Console:
NOTIFICATION J2EE RMI0004 Invalid username or password for Sample(sample). Authentication failed.
Please help,also let me know If I am missing on configuration side or whatever is required.I am using OC4j 10.1.3.
Thanks & Regards
Add the following in system-jazn-data.xml
<grant>
<grantee>
<principals>
<principal>
<type>user</type>
<class>Your Principal Class</class>
<name>UserName to which you want to give permission</name>
</principal>
</principals>
</grantee>
<permissions>
<permission>
<class>com.evermind.server.rmi.RMIPermission</class>
<name>login</name>
</permission>
</permissions>
</grant>
Similar Messages
-
Hi,
I get this message when i tried to run the application after i have deployed the EJBs and the application. When i test the EJBs i am also getting that there is a problem in the JNDI name but everything looks fine in the DD and i have checked them twice!! Its really frustrating me as i have finish some work soon.. if you know what i mean. Any help is appreciated , thanks in advance.The message is----------->> javax.naming.LinkException: [Root exception is javax.naming.NameNotFoundException
-
Hi
I have a startup class which needs to access a local entity bean. It used to work
in weblogic 6.1, i am currently migrating to 8.1 and i get a Link Exception. I
tried to make the startup class as a listener with in the application (EAR), it
still complains.
Since it worked in 6.1 i am sure there should be a way for a startup class to
access a local EJB, please help, i have seen lot of posting regarding this issue
in the newsgroup but no clear answer.
Any one who faced this problem before and had it solved please do repsond ASAP.
U can mail to me at [email protected]
Thanks
SijuAre you sure the EJB deployed with that JNDI name?
Can you show me your weblogic-ejb-jar.xml?
-- Rob
Arun wrote:
Hi,
Do we have a solution for this problem? I am encountering this problem with an
Applciation Lifecycle Listener. I have deployed this Listener with my EAR file
and it accesses a local ejb (stateful) in its postStart() method. The JNDI look
up is causing a LinkException (root exception is NameNotFoundException)
I am not at my work PC but the application was something like this.
"weblogic-application.xml" had something like.
<listener>
<listener-class>MyListener</listener-class>
<listener-uri>mylistener.jar</listener-uri>
</listener>
where mylistener.jar was placed at the root of the EAR file.
MyListener.java was something like,
import weblogic.application.ApplicationLifecycleListener;
import weblogic.application.ApplicationLifecycleEvent;
import mypackage.mylocalhome;
import mypackage.mylocal;
import javax.naming.*;
public class MyListener extends ApplicationLifecycleListener {
public void preStart(ApplicationLifecycleEvent evt) {
System.out.println
("MyListener(preStart) -- we should always see you..");
} // preStart
public void postStart(ApplicationLifecycleEvent evt) {
try {
System.out.println
("MyListener(postStart) -- we should always see you..");
Context ctx = new InitialContext();
mylocalhome localhome = (mylocalhome)ctx.lookup("MYLOCALJNDINAME");
mylocal localobj = localhome.create();
} catch (Exception e) {
e.printStackTrace();
} // postStart
public void preStop(ApplicationLifecycleEvent evt) {
System.out.println
("MyListener(preStop) -- we should always see you..");
} // preStop
public void postStop(ApplicationLifecycleEvent evt) {
System.out.println
("MyListener(postStop) -- we should always see you..");
} // postStop
public static void main(String[] args) {
System.out.println
("MyListener(main): in main .. we should never see you..");
} // main
Any help is greatly appreciated.
Thanks,
Arun
Rob Woollen <[email protected]> wrote:
We'll need some more info. Can you show me your weblogic-ejb-jar.xml,
the code you are using to lookup the bean, and the full exception?
-- Rob
Siju Hariharan wrote:
Hi
I have a startup class which needs to access a local entity bean. Itused to work
in weblogic 6.1, i am currently migrating to 8.1 and i get a Link Exception.I
tried to make the startup class as a listener with in the application(EAR), it
still complains.
Since it worked in 6.1 i am sure there should be a way for a startupclass to
access a local EJB, please help, i have seen lot of posting regardingthis issue
in the newsgroup but no clear answer.
Any one who faced this problem before and had it solved please do repsondASAP.
U can mail to me at [email protected]
Thanks
Siju -
OC4J AuthenticationException: Not authorized
When using the default oc4jadmin username and password with OAS 10.1.3, my RMI connections work properly. However, I tried to create another user similar to that user, but when my code connects, I get the following error in the opmn log.
11/03/21 07:25:00 javax.naming.NamingException: Lookup error: javax.naming.AuthenticationException: Not authorized; nested exception is:
javax.naming.AuthenticationException: Not authorized [Root exception is javax.naming.AuthenticationException: Not authorized]
I have made that new user a member of the OC4J Administrators group, just like oc4jadmin user. Why can't I connect with a similar user? What am I missing?
Thanks,
KrisMaybe this will help someone else...
This pertains to trying to use an alternate user other than the default user "oc4jadmin" for RMI. If you want to use a different user, you must login to the EM tool, then click on the application container link that you want to update. Then go to the Administration tab and click on the "Go to task" link for Security Providers, then click on the Instance Level Security button and then on the Realms tab. In the Users column, the link will most likely say "3", and if you click on the link you'll see a list of users including oc4jadmin. Click the Create button to create your new user and then add them to the oc4j-administrators role. -
Please help ..
I have a working EAR on weblogic app server and deployed it on oracle 10g app server release 2 .. the application is developed in struts .. the following error is shown on the console ..
06/09/22 10:34:28 Start process
06/09/22 10:34:37 log4j:WARN No appenders could be found for logger (org.apache.struts.util.PropertyMessageResources).
06/09/22 10:34:37 log4j:WARN Please initialize the log4j system properly.
06/09/22 10:34:43 INSIDE GET PROPERTY METHOD value for property= org.jnp.interfaces.NamingContextFactory
06/09/22 10:34:43 INSIDE GET PROPERTY METHOD value for property= localhost:1099
06/09/22 10:34:43 Oracle Application Server Containers for J2EE 10g (10.1.2.0.2) initialized
06/09/22 11:04:57 ************Inside eCreditSessionListenerClass Session Created: 0
22 Sep 2006 11:04:57,352 INFO com.ecredit.login.struts.LoginAction - inside getBeanObjec
22 Sep 2006 11:04:57,384 INFO com.ecredit.login.struts.LoginAction - inside getBeanObjec------>Login
22 Sep 2006 11:04:57,399 INFO com.ecredit.login.struts.LoginAction - Exception occured in Throwable Action Classjavax.naming.NamingException: Lookup error: javax.naming.AuthenticationException: Invalid username/password for default (); nested exception is:
javax.naming.AuthenticationException: Invalid username/password for default () [Root exception is javax.naming.AuthenticationException: Invalid username/password for default ()]
22 Sep 2006 11:04:57,399 INFO com.ecredit.login.struts.LoginAction - after getBeanObjec
22 Sep 2006 11:04:57,399 INFO com.ecredit.login.struts.LoginAction - after home
22 Sep 2006 11:04:57,399 INFO com.ecredit.login.struts.LoginAction - Exception occured in Throwable Action Classjava.lang.NullPointerException
22 Sep 2006 11:04:57,415 DEBUG org.apache.struts.action.RequestProcessor - processForwardConfig(ForwardConfig[name=null,path=null,redirect=false,contextRelative=false,module=null])
The code snippet where this error probably occurred is >>>>
private Object getBeanObject(String beanName)
Object objref = null;
try
System.out.println("inside getBeanObjec");
Properties props= new Properties();
props.put(Context.INITIAL_CONTEXT_FACTORY, initial_context_factory);
props.put(Context.PROVIDER_URL,provider_url);
Context initCtx=new InitialContext(props);
System.out.println("inside getBeanObjec------>" +beanName);
objref=initCtx.lookup(beanName);
catch(Exception e)
e.printStackTrace();
return objref;
At the line >>>>>>>>
objref=initCtx.lookup(beanName);
Please help me to get rid of this ......
Thanks in advance
Gurpreet SinghHi
private Object getBeanObject(String beanName)
Object objref = null;
try
System.out.println("inside getBeanObjec");
Context initCtx=new InitialContext();
System.out.println("inside getBeanObjec------>" +beanName);
objref=initCtx.lookup(beanName);
catch(Exception e)
e.printStackTrace();
return objref;
try this pleace
Asanka Priyanjith -
Javax.naming.AuthenticationException: RMIConnection Disconnected
Hi,
I'm having a problem deploying one application in the Enterprise Manager (10g). When i deploy the application, everything works fine, i can enter on the instance, see stadistics of my application, etc
But when i stop the instance, and start again, it throws an error javax.naming.AuthenticationException: RMIConnection Disconnected. And when i try to access to the configuration of my instance, it said me that there's a problem in the authentication, and the admin password must be the same that the oc4j administrator password... and i'm using the same account...
The full trace of the error is the following:
10/06/30 16:46:19 SEVERE: CoreRemoteMBeanServer.fetchMBeanServerEjbRemote Error reading application-client descriptor: Error communicating with server: Lookup error: javax.naming.AuthenticationException: RMIConnection Disconnected; nested exception is:
javax.naming.AuthenticationException: RMIConnection Disconnected; nested exception is:
javax.naming.NamingException: Lookup error: javax.naming.AuthenticationException: RMIConnection Disconnected; nested exception is:
javax.naming.AuthenticationException: RMIConnection Disconnected [Root exception is javax.naming.AuthenticationException: RMIConnection Disconnected] for URL: ormis://servidor:12718/defaultjavax.naming.NamingException: Error reading application-client descriptor: Error communicating with server: Lookup error: javax.naming.AuthenticationException: RMIConnection Disconnected; nested exception is:
javax.naming.AuthenticationException: RMIConnection Disconnected; nested exception is:
javax.naming.NamingException: Lookup error: javax.naming.AuthenticationException: RMIConnection Disconnected; nested exception is:
javax.naming.AuthenticationException: RMIConnection Disconnected [Root exception is javax.naming.AuthenticationException: RMIConnection Disconnected] [Root exception is java.lang.InstantiationException: Error communicating with server: Lookup error: javax.naming.AuthenticationException: RMIConnection Disconnected; nested exception is:
javax.naming.AuthenticationException: RMIConnection Disconnected; nested exception is:
javax.naming.NamingException: Lookup error: javax.naming.AuthenticationException: RMIConnection Disconnected; nested exception is:
javax.naming.AuthenticationException: RMIConnection Disconnected [Root exception is javax.naming.AuthenticationException: RMIConnection Disconnected]]
at oracle.j2ee.naming.ApplicationClientInitialContextFactory.getApplicationContext(ApplicationClientInitialContextFactory.java:127)
at oracle.j2ee.naming.ApplicationClientInitialContextFactory.getInitialContext(ApplicationClientInitialContextFactory.java:117)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:247)
at javax.naming.InitialContext.init(InitialContext.java:223)
at javax.naming.InitialContext.<init>(InitialContext.java:197)
at oracle.oc4j.admin.jmx.client.CoreRemoteMBeanServer.fetchMBeanServerEjbRemote(CoreRemoteMBeanServer.java:468)
at oracle.oc4j.admin.jmx.client.CoreRemoteMBeanServer.<init>(CoreRemoteMBeanServer.java:161)
at oracle.oc4j.admin.jmx.client.RemoteMBeanServer.<init>(RemoteMBeanServer.java:128)
at oracle.oc4j.admin.jmx.client.RemoteMBeanServer.getMBeanServer(RemoteMBeanServer.java:158)
at oracle.oc4j.admin.jmx.client.ClientMBeanServerProxyFactory.getMBeanServer(ClientMBeanServerProxyFactory.java:68)
at oracle.oc4j.admin.jmx.remote.rmi.RMIJMXConnectorImpl.getConnector(RMIJMXConnectorImpl.java:190)
at oracle.oc4j.admin.jmx.remote.JMXConnectorImpl.connect(JMXConnectorImpl.java:400)
at oracle.oc4j.admin.topology.ConnectionRefImpl.getConnector(ConnectionRefImpl.java:241)
at oracle.oc4j.admin.management.farm.mbeans.JVMAgr.getAttribute(JVMAgr.java:1378)
at sun.reflect.GeneratedMethodAccessor39.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at sun.reflect.misc.Trampoline.invoke(MethodUtil.java:36)
at sun.reflect.GeneratedMethodAccessor6.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at sun.reflect.misc.MethodUtil.invoke(MethodUtil.java:239)
at javax.management.modelmbean.RequiredModelMBean.invokeMethod(RequiredModelMBean.java:1071)
at javax.management.modelmbean.RequiredModelMBean.invoke(RequiredModelMBean.java:953)
at oracle.oc4j.admin.jmx.server.mbeans.model.DefaultModelMBeanImpl.invoke(DefaultModelMBeanImpl.java:700)
at com.sun.jmx.mbeanserver.DynamicMetaDataImpl.invoke(DynamicMetaDataImpl.java:213)
at com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:220)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:815)
at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:784)
at oracle.oc4j.admin.jmx.server.state.LocalizationFilterMBeanServer.invoke(LocalizationFilterMBeanServer.java:579)
at oracle.oc4j.admin.jmx.distributed.MBeanServerDelegate.invoke(MBeanServerDelegate.java:495)
at oracle.oc4j.admin.management.farm.mbeans.J2EEServerAgr.getAttribute(J2EEServerAgr.java:1599)
at sun.reflect.GeneratedMethodAccessor38.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at sun.reflect.misc.Trampoline.invoke(MethodUtil.java:36)
at sun.reflect.GeneratedMethodAccessor6.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at sun.reflect.misc.MethodUtil.invoke(MethodUtil.java:239)
at javax.management.modelmbean.RequiredModelMBean.invokeMethod(RequiredModelMBean.java:1071)
at javax.management.modelmbean.RequiredModelMBean.invoke(RequiredModelMBean.java:953)
at oracle.oc4j.admin.jmx.server.mbeans.model.DefaultModelMBeanImpl.invoke(DefaultModelMBeanImpl.java:700)
at com.sun.jmx.mbeanserver.DynamicMetaDataImpl.invoke(DynamicMetaDataImpl.java:213)
at com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:220)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:815)
at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:784)
at oracle.oc4j.admin.jmx.server.state.LocalizationFilterMBeanServer.invoke(LocalizationFilterMBeanServer.java:579)
at oracle.sysman.ias.studio.jmx.spi.JMXConnectorImpl.invoke(JMXConnectorImpl.java:389)
at oracle.sysman.ias.studio.j2ee.shared.jmx.oc4j.ClusterIASJMXUtil.getAttribute(ClusterIASJMXUtil.java:370)
at oracle.sysman.ias.studio.setup.javasso.JMXJavaSSOConfAdminBean.isJssoConfigured(JMXJavaSSOConfAdminBean.java:1041)
at oracle.sysman.ias.studio.setup.javasso.JavaSSOConfHelper.isJssoConfigured(JavaSSOConfHelper.java:802)
at oracle.sysman.ias.studio.cluster.TopologyHelper.prepareData(TopologyHelper.java:1300)
at oracle.sysman.ias.studio.sdk.AbstractController.prepareData(AbstractController.java:875)
at oracle.sysman.emSDK.svlt.PageHandler.handleRequest(PageHandler.java:391)
at oracle.sysman.emSDK.svlt.EMServlet.myDoGet(EMServlet.java:765)
at oracle.sysman.emSDK.svlt.EMServlet.doGet(EMServlet.java:283)
at oracle.sysman.ias.studio.app.StudioConsole.doGet(StudioConsole.java:297)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:743)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
at com.evermind.server.http.ResourceFilterChain.doFilter(ResourceFilterChain.java:64)
at oracle.sysman.ias.studio.app.BrowserVersionFilter.doFilter(BrowserVersionFilter.java:75)
at com.evermind.server.http.EvermindFilterChain.doFilter(EvermindFilterChain.java:15)
at oracle.sysman.ias.studio.app.MultipleJVMFilter.doFilter(MultipleJVMFilter.java:85)
at com.evermind.server.http.EvermindFilterChain.doFilter(EvermindFilterChain.java:17)
at oracle.sysman.ias.studio.app.PostLogonFilter.doFilter(PostLogonFilter.java:80)
at com.evermind.server.http.EvermindFilterChain.doFilter(EvermindFilterChain.java:17)
at oracle.sysman.ias.studio.app.ShortHostnameRedirectFilter.doFilter(ShortHostnameRedirectFilter.java:68)
at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:619)
at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:368)
at com.evermind.server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:866)
at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:448)
at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:302)
at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:190)
at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260)
at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
at java.lang.Thread.run(Thread.java:595)
Caused by: java.lang.InstantiationException: Error communicating with server: Lookup error: javax.naming.AuthenticationException: RMIConnection Disconnected; nested exception is:
javax.naming.AuthenticationException: RMIConnection Disconnected; nested exception is:
javax.naming.NamingException: Lookup error: javax.naming.AuthenticationException: RMIConnection Disconnected; nested exception is:
javax.naming.AuthenticationException: RMIConnection Disconnected [Root exception is javax.naming.AuthenticationException: RMIConnection Disconnected]
at com.oracle.naming.J2EEContext.create(J2EEContext.java:104)
at oracle.j2ee.naming.ApplicationClientInitialContextFactory.getApplicationContext(ApplicationClientInitialContextFactory.java:124)
... 77 more
Caused by: oracle.oc4j.rmi.OracleRemoteException: Lookup error: javax.naming.AuthenticationException: RMIConnection Disconnected; nested exception is:
javax.naming.AuthenticationException: RMIConnection Disconnected; nested exception is:
javax.naming.NamingException: Lookup error: javax.naming.AuthenticationException: RMIConnection Disconnected; nested exception is:
javax.naming.AuthenticationException: RMIConnection Disconnected [Root exception is javax.naming.AuthenticationException: RMIConnection Disconnected]
at oracle.oc4j.deployment.ApplicationClientResourceFinder.lookupResourceFinder(ApplicationClientResourceFinder.java:110)
at oracle.oc4j.deployment.ApplicationClientResourceFinder.getFinder(ApplicationClientResourceFinder.java:123)
at oracle.oc4j.deployment.ApplicationClientResourceFinder.getLocation(ApplicationClientResourceFinder.java:75)
at oracle.oc4j.deployment.ApplicationClientResourceFinder.getEjbBinding(ApplicationClientResourceFinder.java:38)
at com.oracle.naming.J2EEContext.addEJBReferenceEntries(J2EEContext.java:515)
at com.oracle.naming.J2EEContext.create(J2EEContext.java:97)
... 78 more
Caused by: javax.naming.NamingException: Lookup error: javax.naming.AuthenticationException: RMIConnection Disconnected; nested exception is:
javax.naming.AuthenticationException: RMIConnection Disconnected [Root exception is javax.naming.AuthenticationException: RMIConnection Disconnected]
at com.evermind.server.rmi.RMIClientContext.lookup(RMIClientContext.java:64)
at oracle.oc4j.deployment.ApplicationClientResourceFinder.lookupResourceFinder(ApplicationClientResourceFinder.java:101)
... 83 more
Caused by: javax.naming.AuthenticationException: RMIConnection Disconnected
at oracle.oc4j.rmi.ClientRmiTransport.connectToServer(ClientRmiTransport.java:99)
at oracle.oc4j.rmi.ClientSocketRmiTransport.connectToServer(ClientSocketRmiTransport.java:68)
at com.evermind.server.rmi.RMIClientConnection.connect(RMIClientConnection.java:646)
at com.evermind.server.rmi.RMIClientConnection.sendLookupRequest(RMIClientConnection.java:190)
at com.evermind.server.rmi.RMIClientConnection.lookup(RMIClientConnection.java:174)
at com.evermind.server.rmi.RMIClient.lookup(RMIClient.java:283)
at com.evermind.server.rmi.RMIClientContext.lookup(RMIClientContext.java:51)
... 84 more
In bold, there is a clue that can help, but i can't understand :P
Any help would be appreciated
Bye!gday WhiteSox --
You don't say how you are creating the new container -- is this standalone where you've extracted it to another directory and munged the ports, or in an OracleAS instalallation where you created a new instance?
What are you using to perform the deployment operation?
If you post some more details, we can try and help.
cheers
-steve- -
Hello world,
To anybody who receives this irritating error in a Java client
application attempting to access Weblogic Server 6.1 (and possibly
weblogic server 6):
javax.naming.AuthenticationException. Root exception is
java.lang.SecurityException: attempting to add an object which is not
an instance of java.security.Principal to a Subject's Principal Set
The cause of your problem is having JAAS explicitly in your classpath.
It somehow messes up authentication to WebLogic. Remove it and your
problem will disappear.
The complete exception was:
javax.naming.AuthenticationException. Root exception is
java.lang.SecurityException: attempting to add an object which is not
an instance of java.security.Principal to a Subject's Principal Set
at javax.security.auth.Subject$SecureSet.add(Subject.java:1098)
at weblogic.common.internal.BootServicesStub.writeUserInfoToSubject(BootServicesStub.java:72)
at weblogic.common.internal.BootServicesStub.authenticate(BootServicesStub.java:80)
at weblogic.security.acl.internal.Security.authenticate(Security.java:108)
at weblogic.jndi.WLInitialContextFactoryDelegate.pushUser(WLInitialContextFactoryDelegate.java:509)
at weblogic.jndi.WLInitialContextFactoryDelegate.newContext(WLInitialContextFactoryDelegate.java:364)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:336)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:208)
at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:149)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:668)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:246)
at javax.naming.InitialContext.init(InitialContext.java:222)
at javax.naming.InitialContext.<init>(InitialContext.java:198)
at au.com.orrcon.orrconcentral.Application.<init>(Application.java:87)
at au.com.orrcon.orrconcentral.Application.getApp(Application.java:52)
at au.com.orrcon.orrconcentral.orrconCentral.<init>(orrconCentral.java:130)
at au.com.orrcon.orrconcentral.orrconCentral.main(orrconCentral.java:219)Steve Wesemeyer <[email protected]> wrote:
I have encountered the same problem and I do not have JAAS on my classpath
at all (unless it's there by default). Are there any other possible
causes for this?
Cheers,
SteveA note to all who read this thread:
I also had to remove Sun's j2ee (version 1.2) from my client's classpath before
the same problem went away. 1 programmer day down the drain....
Regards,
MG -
Dear all,
i am trying to integrate active directory i am getting LDAP connection error
LDAP Connection Error
javax.naming.AuthenticationException [Root exception is com.tarantella.tta.webservices.TTAException]
and cannot proceed.
i selected on the previous screen as domain controller plus LDAP/Active directory
right
but it is not working
any idea?Hi,
Please try using the User Pricipal Name (UPN) as the username:
username@domein
Also make sure you ldap server url are correct:
ldap://server.domain
not:
ldap://domain
Best Regards,
Arno Staal
Divider B.V. -
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) -
Javax.naming.AuthenticationException
Hi :
I am getting the following exception when I am trying to lookup
a MBeanHome
java.lang.IllegalArgumentException: Invalid user name or password, javax.naming.AuthenticationException
[Root exception is java.lang.SecurityException: attempting to add an object which
is not an instance of java.security.Principal to a Subject's Principal Set]
at weblogic.management.Helper.getMBH(Helper.java:62)
at weblogic.management.Helper.getAdminMBeanHome(Helper.java:28)
at TestMBeanHome.main(TestMBeanHome.java:9)
I am doing a simple lookup, like so...
MBeanHome home = (MBeanHome)Helper.getAdminMBeanHome("system", "password", "t3://localhost:7001"
The login/password work through the console.
Any help is appreciated
--krishYou should be able to get the MBeanHome with the Helper class if the system
username, pwd are correct.
unless you have put some ACLs on MBeans and restricted the access for some
specific users....
Are you sure that your system user's password is: "password" ?
I wrote a small prog to check the method and it returns the mbeanHome
correctly ....
I have attached it below ....
hope it helps,
Mihir
import weblogic.management.Helper;
import weblogic.management.*;
import javax.management.*;
public class useHelper {
public static String SERVER_NAME="myserver";
public static weblogic.management.MBeanHome localHome = null;
public static weblogic.management.MBeanHome adminHome = null;
public static void main(String[] args) {
useHelper.find("172.17.26.33", 7001, "mihirk00");
public static void find(String host, int port, String password) {
String url = "t3://" + host + ":" + port;
try {
localHome = (MBeanHome)Helper.getMBeanHome("system", password,
url, SERVER_NAME);
adminHome = (MBeanHome)Helper.getAdminMBeanHome("system",
password, url);
System.out.println("Local and Admin Homes " + "found using the
Helper class: " + localHome + " " + adminHome);
} catch (IllegalArgumentException iae) {
System.out.println("Illegal Argument Exception: " + iae);
"Krish Garimella" <[email protected]> wrote in message
news:[email protected]...
>
Hi :
I am getting the following exception when I am trying to lookup
a MBeanHome
java.lang.IllegalArgumentException: Invalid user name or password,javax.naming.AuthenticationException
[Root exception is java.lang.SecurityException: attempting to add an
object which> is not an instance of java.security.Principal to a Subject's PrincipalSet
at weblogic.management.Helper.getMBH(Helper.java:62)
at weblogic.management.Helper.getAdminMBeanHome(Helper.java:28)
at TestMBeanHome.main(TestMBeanHome.java:9)
I am doing a simple lookup, like so...
MBeanHome home = (MBeanHome)Helper.getAdminMBeanHome("system", "password","t3://localhost:7001"
The login/password work through the console.
Any help is appreciated
--krish -
Javax.naming.AuthenticationException [LDAP: error code 49 - 80090308
i am getting a problem in connection.
javax.naming.AuthenticationException: [LDAP: error code 49 - 80090308: LdapErr: DSID-0C090334, comment: AcceptSecurityContext error, data 525, vece
plz suggestsatish_dhn wrote:
plz suggesterr code 49 means problem with login credentials.
"525" (between "data" and "vece" ) means user not found. -
Javax.naming.AuthenticationException: No such domain/application:
I'm trying on JDeveloper 11g tutorial on "Build a Web Application with JDeveloper 11g Using EJB, JPA, and JavaServer Faces. I encounter this problem when try to run the simple java client created by Jdeveloper.
javax.naming.AuthenticationException: No such domain/application: "current-workspace-app"
at oracle.oc4j.rmi.ClientRmiTransport.connectToServer(ClientRmiTransport.java:120)
at oracle.oc4j.rmi.ClientSocketRmiTransport.connectToServer(ClientSocketRmiTransport.java:70)
at com.evermind.server.rmi.RMIClientConnection.connect(RMIClientConnection.java:720)
at com.evermind.server.rmi.RMIClientConnection.sendLookupRequest(RMIClientConnection.java:252)
at com.evermind.server.rmi.RMIClientConnection.lookup(RMIClientConnection.java:235)
at com.evermind.server.rmi.RMIClient.lookup(RMIClient.java:302)
at com.evermind.server.rmi.RMIClientContext.lookup(RMIClientContext.java:64)
at javax.naming.InitialContext.lookup(InitialContext.java:351)
at mssql.HRFacadeClient.main(HRFacadeClient.java:13)
Anyone knows what's the cause of this error? I follow exactly the steps in Jdeveloper 11g tutorial. The only difference is that my database is MS SQL database.Same error.
The real application (web and ejb's) are running on the same OC4J instance. The Web client are accessing the ejb's on port 3101, so i think this is the correct rmi port.
The server is a part of an infrastructure that are running on the same server, the server is one of two ApplicationServers that the infrastructure (farm) is controlling.
each server has an instance name, the server i was deplying to has name instance2. Maybe i have to give a reference to to the instance? -
Sir/Madam,
i am working on Windows Platform and I am getting this error when i want ot configure the LDAP.
Please suggest
javax.naming.AuthenticationException: [LDAP: error code 49 - Invalid Credentials]
at com.sun.jndi.ldap.LdapCtx.mapErrorCode(LdapCtx.java:3005)
at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2951)
at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2753)
at com.sun.jndi.ldap.LdapCtx.connect(LdapCtx.java:2667)
at com.sun.jndi.ldap.LdapCtx.<init>(LdapCtx.java:287)
at com.sun.jndi.ldap.LdapCtxFactory.getUsingURL(LdapCtxFactory.java:175)
at com.sun.jndi.ldap.LdapCtxFactory.getUsingURLs(LdapCtxFactory.java:193)
at com.sun.jndi.ldap.LdapCtxFactory.getLdapCtxInstance(LdapCtxFactory.java:136)
at com.sun.jndi.ldap.LdapCtxFactory.getInitialContext(LdapCtxFactory.java:66)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
at javax.naming.InitialContext.init(InitialContext.java:223)
at javax.naming.InitialContext.<init>(InitialContext.java:197)
at javax.naming.directory.InitialDirContext.<init>(InitialDirContext.java:82)
at TestClient.main(TestClient.java:33)
Thanks in advance.
Regards
Neelamadhabjavax.naming.AuthenticationException: [LDAP: error code 49 - Invalid Credentials]LDAP is rejecting your credentials (username / password). Make sure your credentials are coorectly given, otherwise get help from LDAP admin.
regards,
Sekar -
Javax.naming.* Not Found
I have downloaded the j2sdkee1.3 for comiling my Ejb files.All the files get compiled but my client file which uses javax.naming package doesnt get compiled.The error message says its unable to find javax.naming package. Can somebody help me on this issue please.
Thanxi too am having the same problem any suggestions???
-
Class javax.naming.InitialContext not find import
how should I set the classpath environment?
Where to find javax.naming.InitialContext package?
thanks for you helpYou should set the classpath environment to include wherever your javax.naming package is. If you're using Java 1.3 or later, javax.naming should be in the classpath already.
Maybe you are looking for
-
Error message when Saving as Disc Image & Burning
I've been getting this error message: Not enough free disk space for encoding the remaining assets. When I'm either trying to Burn a DVD or Save as a Disc Image. I've read all of the previous discussions and nothing is working. I have 320 GB on my co
-
HT2688 Can I install iTunes on an external drive and store my music there?
I am trying to figure out the best way to manage my music. 600 cds that I need to upload somewhere. I am thinking I put them in itunes and then bluetooth them to a wireless speaker. My old school stereo needs to go but I am not sure where to beg
-
Checking the size of Oracle XE Database
Hi, I installed oracle 10g express edition on a Linux machine couple of weeks ago. Installation was successful oracle is running fine. Now I am concious about the limitation of 4 GB data size in XE. DBConsole is not running, i am working on it. But w
-
ArcSDE register sdo_gtype of 3003, etype 1005 in Oracle sdo_geometry
1) Has anyone registered data with SDE sdelayer -o register that has the noted gtype and etype? 2) What sdelayer e- entity type(s) should we use, so we can view it with Arc tools? 3) No where does it say this won't work with SDE. 4) The data comes fr
-
I want to print front to back but the software always returns to back to front.
In Hp C4795 I want the print to be front to back , I hit the button for that to happen. I close out and use the printer. It prints back to front. No matter how many times I change it.