The servlet and EJB containers use separate authentication mechanisms
currently. This is due to two different JNDI implementations that haven't
been merged internally. This will be fixed in SP2 or SP3. For now, the
servlet must authenticate itself with the EJB server pretty much just like
an external client would. And the EJB and servlet containers must both be
configured with the users, roles and passwords for your user(s). Did you
look at sample 9a in the Samples guide and in the samples directory? That
example is specifically to show how to do a servlet-->EJB authentication in
JRun.
Scott Stirling
Allaire
-----Original Message-----
From: Terry Dexter [mailto:[EMAIL PROTECTED]]
Sent: Thursday, December 07, 2000 12:07 PM
To: JRun-Talk
Subject: custom servlet authentication -> ejb handoff
I have a custom servlet authentication which is working fine. When I go to
access my EJBs I'm not able to get through. First, do I need to
reauthenticate the user for the EJB container or does the servlet and EJB
containers talk to each other for authentication? The latter seems to be
the case for the default implementation but my custom authenticaion
(isPrincipalInRole) isn't getting called. If it's passed is there a special
way to call new InitialContext()? If not, can I manually pass the
AuthenticatedPrincipal in somehow?
I've honestly looked in the docs and can't find anything. Maybe I didn't
look in the right place.
Any pointers or comments would be well appreciated.
Thanks,
Terry
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Your ad could be here. Monies from ads go to support these lists and provide more
resources for the community. http://www.fusionauthority.com/ads.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
