Hi Jorge, In security scenario 15 we are using secure conversation. In secure conversation we are establishing a security context before actual messages are exchanged. I am not sure whether following error has any relevancy to establishing a security context. It will be great if you could monitor messages exchanged between eclipse client and ESB proxy and let us know. In the mean time we will try to reproduce this scenario in our environment. Also provide us the XACML policy you used in this test.
Thanks AmilaJ On Mon, Feb 21, 2011 at 9:21 AM, Jorge Infante Osorio <[email protected]> wrote: > Hi all. > > I implement a proxy Service like this [1] with security scenario 15, and I > can use the token issued by IS and pass to the ESB, this work fine. > I see that the entitlement mediator work fine, it login into the ESB and the > XACML policy response PERMIT. > > In the WSAS SOAP tracer I see all the request from ESB: > > <soapenv:Envelope xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope";> > <soapenv:Body > xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurit > y-utility-1.0.xsd" wsu:Id="Id-31168594"> > <ns1:greet xmlns:ns1="http://www.wso2.org/types";> > <name>jorge infante 3</name> > </ns1:greet> > </soapenv:Body> > </soapenv:Envelope> > > This request message came without the security header, so the header > mediator work fine. > > And all the WSAS response are the same: > > <soapenv:Envelope xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope";> > <soapenv:Header /> > <soapenv:Body> > <ns:greetResponse xmlns:ns="http://www.wso2.org/types";> > <return>Hello World, jorge infante 3 !!!</return> > </ns:greetResponse> > </soapenv:Body> > </soapenv:Envelope> > > But in the Eclipse console I see this errors in all the call I made: > > Response for Call 1: > Exception in thread "main" org.apache.axis2.AxisFault: InputStream cannot be > NULL. > > Response for call 2: > Exception in thread "main" org.apache.axis2.AxisFault: SOAP header missing > > Response for call 3: > <ns:greetResponse xmlns:ns="http://www.wso2.org/types"; > xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope"; > xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurit > y-utility-1.0.xsd"> > <return> > Hello World, jorge infante 3 !!! > </return> > </ns:greetResponse> > > Response for call 4: > Exception in thread "main" org.apache.axis2.AxisFault: InputStream cannot be > NULL. > > And so on, the response are not the same in every call, so I wondering what > could be the root cause of this behavior. > > > [1] the proxy service: > <proxy xmlns="http://ws.apache.org/ns/synapse"; name="Secureproxy3" > transports="https http" startOnLoad="true" trace="disable" > statistics="enable"> > <target> > <endpoint > name="endpoint_urn_uuid_BB1AB9F8608F7EC366271152455486681545818807"> > <address uri="http://127.0.0.1:9763/services/HelloService/"/> > </endpoint> > <inSequence> > <entitlementService > remoteServiceUrl="https://localhost:9463/services/"; > remoteServiceUserName="admin" remoteServicePassword="admin"/> > <header > xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecuri > ty-secext-1.0.xsd" name="wsse:Security" action="remove"/> > <send/> > </inSequence> > <outSequence> > <log level="full"/> > <send/> > </outSequence> > <faultSequence> > <log level="full"/> > </faultSequence> > </target> > <publishWSDL uri="http://127.0.0.1:9763/services/HelloService?wsdl"/> > <policy > key="conf:/repository/axis2/service-groups/Secureproxy3/services/Secureproxy > 3/policies/SecConSgnEncrUsername"/> > <enableSec/> > </proxy> > > > Ing. Jorge Infante Osorio. > J´Dpto Soluciones SOA. > CDAE. > UCI > > > _______________________________________________ > Carbon-dev mailing list > [email protected] > http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > _______________________________________________ Carbon-dev mailing list [email protected] http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
