Unfortunatly not. We need to separate the durable subscriptions from the same state as the users/roles. The key part is determining the <client-id> for a user.
I made a start in 3.2 on a jdbc statemanager that uses an extended version of the DB schmea required for the DatabaseLoginModule. It is not tested as yet (It does pass the testsuite). Regards, Adrian On Fri, 2003-08-29 at 03:20, [EMAIL PROTECTED] wrote: > I was wondering why the user authorization/authentication with JBossMQ > was configured through this jbossmq-state.xml file (In JBoss 3.0.5) > and not through a more standard JAAS security domain? > > Another way to ask the question is: can I use the JBossSX login > modules (like the LdapLoginModule) for the JBossMQ > authentication/authorization instead of having all the user and roles > defined in the jbossmq-state.xml? If yes, any pointers will be > appreciated. > > Thanks. > > Thomas Cherel ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
