Ok. I have a hacked up version of JMSContainerInvoker working. Now currently we have mdb-user,mdb-password and mdb-subscription-id in the jboss.xml. These are used for durable subscriptions and are referenced in jbossmq-state.xml. Now should we add mdb-role and re-use this fields or should we add new elements say mdb-principal mdb-credentials and mdb-role?
Scott M Stark wrote: > Also, it should be the JMSContainerInvoker, not the Athorization interceptor > that is dealing with obtaining the principal info from the JMS layer. > > ----- Original Message ----- > From: "Scott M Stark" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Thursday, January 31, 2002 11:04 AM > Subject: Re: [JBoss-dev] JAAS with MDB > > > >>No, the standard JMS Message interface needs to be used to obtain >>a configurable principal and credential property. Any JMS provider >>may be used with MDBs. >> >>----- Original Message ----- >>From: "Dave Smith" <[EMAIL PROTECTED]> >>To: "Scott M Stark" <[EMAIL PROTECTED]> >>Cc: <[EMAIL PROTECTED]> >>Sent: Thursday, January 31, 2002 10:51 AM >>Subject: Re: [JBoss-dev] JAAS with MDB >> >> >> >>>OK. So I had a quick peek at the SpyMessage and there is a field called >>>producerClientId that should do the trick. So I add an interceptor in >>>front of the security interceptor that takes the first argument of the >>>invoke , casts to a SpyMessage, grabs the id and sets the Principal in >>>the method invocation and continues along the chain. >>> >>>Will the only type of message delivered to the invoker be a SpyMessage? >>>or can it handle other messages that could cause a class cast error? >>> >>> >>> >>> >>>Scott M Stark wrote: >>> >>> >>>>Authentication and Authorization need to be two seperate security >>>>interceptors. Authentication needs to validate the principal and >>>> >>associate >> >>>>the Subject with the MethodInvocation. The Authorization interceptor >>>>will handle role based permissions and run-as identities. The default >>>>MDB interceptor chain should not include an Authentication >>>> > interceptor. > >>>>If the jboss.xml metadata is enchanced to allow for caller identity to >>>>be obtained from the JMS msg than the container invoker will associate >>>>this information with the call and the Authentication interceptor can >>>> > be > >>>>added to the interceptor chain. >>>> >>>> >> >> >>_______________________________________________ >>Jboss-development mailing list >>[EMAIL PROTECTED] >>https://lists.sourceforge.net/lists/listinfo/jboss-development >> >> > > > _______________________________________________ > Jboss-development mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-development > > _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
