On Wed, 29 Oct 2003 02:21, Adrian Brock wrote:
> This works by wrapping the real connection factory. The wrapper's
> createTopicConnection() is redirected to the real connection factory's
> createTopicConnection(user, passwd); passing the jaas user/credential.
Great, thanks. I thought there had to
On Tue, 2003-10-28 at 12:56, Brian Wallis wrote:
> I have another question, this time about JAAS and JMS.
>
> If I am a client app and login via JAAS (using the clientloginmodule) and then
> I want to subscribe to a JMS topic. As far as I can tell the JAAS login info
> (principal/credential) is
I have another question, this time about JAAS and JMS.
If I am a client app and login via JAAS (using the clientloginmodule) and then
I want to subscribe to a JMS topic. As far as I can tell the JAAS login info
(principal/credential) is not used and I have to specify the
username/password for
On rereading, you would need to allow for unauthenticated users to
map to an identity. This is supported by the unauthenticatedIdentity
login module option as shown for the jbossmq configuration:
flag = "required">
guest
jboss.mq:service=StateManager
Why isn't the run-as role working for this? This is the authorization
role the mdb assumes for all secure calls it makes.
--
Scott Stark
Chief Technology Officer
JBoss Group, LLC
Brian Wallis wrote:
OK, I know, this is a FAQ (or should be) but I ca
OK, I know, this is a FAQ (or should be) but I cannot find the answer.
I have an MDB. It is configured for a durable subscription using mdb-user,
mdb-password in jboss.xml and it has a security-identity/run-as/role-name in
the ejb-jar.xml.
But, it needs to call into an entity bean and needs to
