--- david sims <[EMAIL PROTECTED]> wrote:
> On Wed, 03 May 2000, Alex Cachia wrote:
> > I've been thinking about how to do this in any way let alone a portable
> way.
> > My problem is that I can't seem to get my hands on the password for the
> user
> > returned by getCallerPrincipal(). If I could do that I could use the
> pooled
> > connections and "bind" to the database (well in my case it's a directory,
> but
> > should be the same) when the per caller principle connection is needed.
>
> Couldn't you just look up the user's password in your database, using some
> kind
> of "system" database connection?
That might be a neat solution. I'm increasing the access to the directory, but
that might be an interm solution.
> It's not addressed by the spec, but you could also hang onto the user's
> password at the time he logs into the container (how to do this is
> vendor-specific). Then you could re-use it then.
I'm using weblogic. They use a concept of a realm to do server container
authentication. I'm wondering if I create a session bean from within the realm
object, after the user has be authenticated, if the session bean will be
associated with that users session.
I have a real proplem then because I somehow need to lookup the session bean
from within an entity bean to obtain a password to use to bind to the
directory, since I don't have a reference to the session bean within my entity
bean.
That is what I really need is some why to add to the EntityContext, but ...
Thanks,
Alex
__________________________________________________
Do You Yahoo!?
Send instant messages & get email alerts with Yahoo! Messenger.
http://im.yahoo.com/
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
