[
https://jira.jboss.org/jira/browse/JBESB-2324?page=com.atlassian.jira.plu...
]
Daniel Bevenius commented on JBESB-2324:
----------------------------------------
Not sure if I understand what the issue ishere. Let me explain...
I've modified the security_basic quickstart and using the attachted jboss-esb.xml
'ant runtest'
This is the output on server console (with some comments):
12:29:45,254 INFO [STDOUT] In Service1 (jms transport secured): <-- Service is
secured using jms transport
12:29:45,254 INFO [STDOUT] [Message payload example(just a String) ].
12:29:45,255 INFO [STDOUT] Subject in MyListenerAction : Subject:
Principal: esbuser
Principal: Roles(members:esbrole)
12:29:45,322 INFO [STDOUT] In Service2 (jms transport secured): <-- Service
is secured using jms transport
12:29:45,322 INFO [STDOUT] [Message payload example(just a String) ].
12:29:45,323 INFO [STDOUT] Subject in MyListenerAction : Subject:
Principal: esbuser
Principal: Roles(members:esbrole)
12:29:45,371 INFO [STDOUT] In Service3 (invm transport non-secured): <-- Service is
not secured using invm transport
12:29:45,371 INFO [STDOUT] [Message payload example(just a String) ].
12:29:45,371 INFO [STDOUT] Subject in MyListenerAction : null <--
Subject not accessible to action pipeline
12:29:45,412 INFO [STDOUT] In Service4 (invm transport secured): <-- Service
is secured using invm transport
12:29:45,412 INFO [STDOUT] [Message payload example(just a String) ].
12:29:45,412 INFO [STDOUT] Subject in MyListenerAction : Subject: <-- Subject
is accessible to action pipeline
Principal: esbuser
Principal: Roles(members:esbrole)
So we are removing the context only so that the pipeline cannot access it but using the
ServiceInvoker (through StaticRouter).
Did I miss something here?
ServiceInvoker clears security thread local context during post
---------------------------------------------------------------
Key: JBESB-2324
URL:
https://jira.jboss.org/jira/browse/JBESB-2324
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Rosetta, Security
Affects Versions: 4.4 CP1, 4.5
Reporter: Kevin Conner
Assignee: Daniel Bevenius
Fix For: 4.4 CP2, 4.5
Attachments: jboss-esb.xml
Subsequent invocations of ServiceInvoker will no longer have access to the context.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira