Deploy the bean twice, one with a security domain and one without. Specify the home interfaces for the unsecured bean to be under the java: JNDI context so that they are only usable from inside of the server.
xxxxxxxxxxxxxxxxxxxxxxxx Scott Stark Chief Technology Officer JBoss Group, LLC xxxxxxxxxxxxxxxxxxxxxxxx ----- Original Message ----- From: "Fee Ling Chin" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, July 31, 2002 2:13 PM Subject: [JBoss-user] Session bean (client and server side) security question > Hi, > > What is the best way to access a session bean with 2 different security > domains? Let's say I want external clients to authenticate and get > authorization to call a session bean method but I don't want to impose any > security for other server components to access the same session bean. > Basically I want to secure the bean for client applications but not on the > server. > > I am familiar with setting up JBoss security and I probably can create a > private and public session beans to do this but I think there is a better > approach than this solution. > > Thanks in advance. > Fee > > > ------------------------------------------------------- > This sf.net email is sponsored by: Dice - The leading online job board > for high-tech professionals. Search and apply for tech jobs today! > http://seeker.dice.com/seeker.epl?rel_code=31 > _______________________________________________ > JBoss-user mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-user > ------------------------------------------------------- This sf.net email is sponsored by: Dice - The leading online job board for high-tech professionals. Search and apply for tech jobs today! http://seeker.dice.com/seeker.epl?rel_code=31 _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
