First; to use a new EJB with the EJBUserManager you only need to use an EJB
where the bean implements UserEJB (ie it's remote extends upon that
interface), that's the solution most customers wanting to do this (using
their own EJBs as the source of user info). If you dont use username as
primary key you can add a "findByUsername" method in the home interface
which will in that case be used.
The EJBUserManager creates the InitialContext instance in the init(...)
method (where the context exists). There should "always" be a context when
the usermanager is called though - this wasnt always the case in 0.9.6 but
all instances where this occur has been fixed in the latest internal jar.
Hope it helps. :)
/Magnus Stenman, the Orion team
----- Original Message -----
From: "Nick Newman" <[EMAIL PROTECTED]>
To: "Orion-Interest" <[EMAIL PROTECTED]>
Sent: Monday, April 24, 2000 6:16 PM
Subject: Custom UserManager - naming context
> I would like to be able to log on to an Orion web-application by verifying
> the password against an encrypted value (as in a regular unix password
> file). It seems that to do this I must provide custom implementations of
> the UserManager and the User interfaces, and indeed I can get a solution
to
> work in this way.
>
> I would prefer to use a solution in which an entity EJB acted as an
> interface to the password table, but I do not know how to access an EJB's
> home interface from within the UserManager code. If I try the usual
scheme
> I get a NamingException saying "Not in application scope", which is true.
>
> The EJBUserManager supplied with Orion must overcome this same problem, so
> it must be possible, but I don't have access to its code. Any ideas?
>
> Thanks,
> Nick
