Thanks. It does help.
Thomas Cherel
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
Sent: Friday, August 29, 2003 5:00
AM
To:
[EMAIL PROTECTED]
Subject: Antwort: [JBoss-user]
User authorization/authentication with JBossMQ
Maybe this will
Unfortunatly not. We need to separate the durable subscriptions
from the same state as the users/roles. The key part is determining
the 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
l.: 04331- 69 37 43
Fax: 04331- 69 28 99
Besucheradresse: Wollinstr. 10
[EMAIL PROTECTED]
Gesendet von: [EMAIL PROTECTED]
29.08.2003 04:20
Bitte antworten an jboss-user
An: [EMAIL PROTECTED]
Kopie:
Thema: [JBoss-user] User author
Title: User authorization/authentication with JBossMQ
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
