Re: JNDI SecurityException

2001-03-27 Thread Tim Endres
> >I have no idea. I simply know that someone on the list claimed to have reported this > >bug, and to this day my servlets simply will not properly authenticate. I do not >know > >if this is a problem with just servlets, or anything using ApplicationClient{ICF}. >Our > >servlets are running in

Re: JNDI SecurityException

2001-03-27 Thread Eric Anderson
>> I tried the ApplicationClientInitialContextFactory (by mistake) when I first set >this up. >> I just gave me other problems (I think there was some sort of complaint about a >missing >> application.xml file). > >I believe this complaint is because it is looking for META-INF/application-clie

Re: JNDI SecurityException

2001-03-26 Thread Tim Endres
> I tried the ApplicationClientInitialContextFactory (by mistake) when I first set >this up. > I just gave me other problems (I think there was some sort of complaint about a >missing > application.xml file). As far as I know, there should be no reason that I cannot >use the > RMIInitialConte

RE: JNDI SecurityException

2001-03-26 Thread Eric Anderson
Hi Nimret, >this is funny - it took me a whole week to get this right +) That's not funny! That means that the documentation is seriously inadequate! >> System.setProperty("java.naming.factory.initial","com.evermind >.server.rmi.RMIInitialContextFactory"); > >this should be different .. check

Re: JNDI SecurityException

2001-03-26 Thread Eric Anderson
I tried the ApplicationClientInitialContextFactory (by mistake) when I first set this up. I just gave me other problems (I think there was some sort of complaint about a missing application.xml file). As far as I know, there should be no reason that I cannot use the RMIInitialContextFactory f

Re: JNDI SecurityException

2001-03-26 Thread Eric Anderson
Hi, I just tried this. No change: SecurityException - invalid username/password for PersonBean. Tnx, Eric -- On Mon, 26 Mar 2001 13:22:56 KirkYarina wrote: >System.setProperty("java.naming.provider.url","ormi://192.168.100.3/appname"); >

Re: JNDI SecurityException

2001-03-26 Thread Eric Anderson
No, the admin user in this case is not deactivated. There's no deactivated attribute on that element anyway, so I'm assuming that the default is 'activated' as you say. Thanks, Eric -- On Mon, 26 Mar 2001 13:29:38 Ray Harrison wrote: >Don't know if this is the case, but look in your %ORION_

Re: JNDI SecurityException

2001-03-26 Thread Ray Harrison
Don't know if this is the case, but look in your %ORION_DIR/config/principals.xml and look at the user entry for admin. Check to make sure that deactivated="false" in the admin description section as below: The default administrator

Re: JNDI SecurityException

2001-03-26 Thread Tim Endres
First, have you tried using ApplicationClientInitialContextFactory as opposed to RMIInitialContextFactory? Second, I believe it is a known bug in Orion that servlet's do not properly send their user/password information to the app server. In other words, Servlet InitialContext authentication is br

RE: JNDI SecurityException

2001-03-26 Thread Nimret Sandhu
hi eric ~ this is funny - it took me a whole week to get this right +) > System.setProperty("java.naming.factory.initial","com.evermind .server.rmi.RMIInitialContextFactory"); this should be different .. check the jndi.properties file i am sending along with this msg. > System.setProperty("jav

Re: JNDI SecurityException

2001-03-26 Thread KirkYarina
System.setProperty("java.naming.provider.url","ormi://192.168.100.3/appname"); ^^ Try this; it was just discussed ( http://www.mail-archive.com/orion-interest%40orionserver.com/msg11568.

JNDI SecurityException

2001-03-26 Thread Eric Anderson
I'm trying to re-deploy an existing CMP bean on Orion and am having no luck at all with the JNDI lookup of the bean's home interface. No matter what I change or what I try, I *always* get a SecurityException saying that the userid/password is invalid. The principal and credentials that I am