]On Behalf Of Tim Endres
Sent: Tuesday, November 21, 2000 7:07 PM
To: Orion-Interest
Cc: Arved Sandstrom
Subject: RE: -- Arved -- Can you please help me with servlet
authentication?
Hi Arved,
Although we have a single servlet front-end, and do programmatic
usermanagement (including login), the a
You'll understand that we are using 100% programmatic user management. Also,
I think (in your last few paras) that you are close to answering your own
question. If you've got multiple users and you cannot rely on a
jndi.properties, then by exclusion you must rely on the users to supply
their
Although we have a single servlet front-end, and do programmatic
usermanagement (including login), the actual user manager and role manager
stuff all happens down in EJB-land (in a session bean being referenced from
the servlet). So we do not use JNDI properties at all for authentication,
except
Incidentally, the location of jndi.properties, and how it works, is
dictated
by Java (I think starting with JDK 1.2, but it could have been 1.3). If
there exists a jndi.properties in your classpath, it will get read. So
this
behaviour is entirely independent of J2EE.
this might also have to
Hi Arved,
Although we have a single servlet front-end, and do programmatic
usermanagement (including login), the actual user manager and role manager
stuff all happens down in EJB-land (in a session bean being referenced from
the servlet). So we do not use JNDI properties at all for
