Hide Forgot
Date of First Response: 2009-03-16 17:08:41 project_key: SOA Because of the https://jira.jboss.org/jira/browse/SOA-941, now in the JBoss ESB, it will propagate the security information internally, so won't need to specify it explicitly in the opensso quick start example.
fixed by revision 2151 of soa-p repository.
Reopen the issue, it seems that it doesn't work if I simply remove that action, tested against soa-p 4.3 CR1. Need to work on it again.
The error message when it tries to access the EJB3 service. 17:00:50,430 INFO [STDOUT] In Service3: 17:00:50,431 INFO [STDOUT] [Message payload example(just a String) ]. 17:00:50,431 INFO [STDOUT] Subject in EjbClientAction : Subject: Principal: SSOToken [ssoToken=AQIC5wM2LY4Sfcz7Svx3mPoZPKACJuzsO7AIW8bwFqCvMFw=@AAJTSQACMDE=#] Principal: [groupName=Roles, members=[[roleName=adminRole]]] 17:00:50,573 INFO [OpenSSOLoginModule] Has valid OpenSSO session : false 17:00:50,701 ERROR [STDERR] [Fatal Error] :4:23: The value of attribute "message" associated with an element type "Exception" must not contain the '<' character. 17:00:50,759 WARN [ActionProcessingPipeline] No fault address defined for fault message! To: InVMEpr [ PortReference < <wsa:Address invm://4f70656e53534f5365727669636533/false?false#10000/>, <wsa:ReferenceProperties jbossesb:passByValue : false/>, <wsa:ReferenceProperties jbossesb:type : urn:jboss/esb/epr/type/invm/> > ] MessageID: f965e22f-fc26-43e1-ac01-45fd90126091 RelatesTo: jms:correlationID#f965e22f-fc26-43e1-ac01-45fd90126091 17:00:50,790 INFO [ServiceInvoker] Subject in ServiceInvoker Subject: Principal: SSOToken [ssoToken=AQIC5wM2LY4Sfcz7Svx3mPoZPKACJuzsO7AIW8bwFqCvMFw=@AAJTSQACMDE=#] Principal: [groupName=Roles, members=[[roleName=adminRole]]]
Link: Added: This issue depends JBESB-2126
Verified in 4.3 CP01 CR4: 2009-03-16 16:17:52,576 INFO [org.jboss.soa.esb.services.security.SecurityServiceFactory] Using [org.jboss.internal.soa.esb.services.security.JaasSecurityService] as the SecurityService implementation. 2009-03-16 16:17:52,629 INFO [org.jboss.soa.security.opensso.OpenSSOLoginModule] Has valid OpenSSO session : false 2009-03-16 16:17:54,353 INFO [org.jboss.soa.security.opensso.OpenSSOLoginModule] Login succeeded. 2009-03-16 16:17:54,484 INFO [STDOUT] In Service1: 2009-03-16 16:17:54,484 INFO [STDOUT] [Message payload example(just a String) ]. 2009-03-16 16:17:54,484 INFO [STDOUT] Subject in MyJMSListenerAction : Subject: Principal: SSOToken [ssoToken=AQIC5wM2LY4SfcxGz8TWw39GHVkBE/xW51QiN6QUSewasvk=@AAJTSQACMDE=#] Principal: [groupName=Roles, members=[[roleName=adminRole]]] 2009-03-16 16:17:54,530 INFO [STDOUT] In Service2: 2009-03-16 16:17:54,530 INFO [STDOUT] [Message payload example(just a String) ]. 2009-03-16 16:17:54,531 INFO [STDOUT] Subject in MyJMSListenerAction : Subject: Principal: SSOToken [ssoToken=AQIC5wM2LY4SfcxGz8TWw39GHVkBE/xW51QiN6QUSewasvk=@AAJTSQACMDE=#] Principal: [groupName=Roles, members=[[roleName=adminRole]]] 2009-03-16 16:17:54,575 INFO [STDOUT] In Service3: 2009-03-16 16:17:54,576 INFO [STDOUT] [Message payload example(just a String) ]. 2009-03-16 16:17:54,576 INFO [STDOUT] Subject in EjbClientAction : Subject: Principal: SSOToken [ssoToken=AQIC5wM2LY4SfcxGz8TWw39GHVkBE/xW51QiN6QUSewasvk=@AAJTSQACMDE=#] Principal: [groupName=Roles, members=[[roleName=adminRole]]] 2009-03-16 16:17:54,730 INFO [STDOUT] SimpleSLSB printMessage : from ESB 2009-03-16 16:17:54,730 INFO [STDOUT] SimpleSLSB Caller principal: SSOToken [ssoToken=AQIC5wM2LY4SfcxGz8TWw39GHVkBE/xW51QiN6QUSewasvk=@AAJTSQACMDE=#] 2009-03-16 16:17:54,733 INFO [STDOUT] isCallerInRole('adminRole') : true