How are you configuring the STSClients for your tests? What does a sample SOAP request to the STS look like?
Colm. On Mon, Aug 14, 2017 at 5:53 PM, mdefazio <[email protected]> wrote: > Hello, > > I am currently upgrading my STSClients to use CXF 3.1.12 (Previous version > was 3.0.1). > > I created a test driver that runs from a executable jar to run my > integration tests using CXF 3.1.12 and java8 > > I am currently getting a client side interceptor Fault after requesting a > token from the STS saying that my STS soap response contained > RequestSecurityTokenResponse element and my client expected the element > RequestSecurityTokenResponseCollection. > > The wsdl hosted by my STS Contains the following operation: > > <wsdl:portType name="STS"> > ... > <wsdl:operation name="Issue"> > <wsdl:input message="tns:RequestSecurityTokenMsg" > wsam:Action="http://docs.oasis-open.org/ws-sx/ws-trust/200512/RST/Issue"; > /> > <wsdl:output message="tns:RequestSecurityTokenResponseCollectionMsg" > wsam:Action="http://docs.oasis-open.org/ws-sx/ws-trust/ > 200512/RSTRC/IssueFinal" > /> > </wsdl:operation> > ... > </wsdl:portType> > > From the WSDL, looks like it should be returning the > RequestSecurityTokenResponseCollection type but I don't know why > RequestSecurityTokenResponse is being returned to the STSClientinstead of > RequestSecurityTokenResponseCollection. > > I found a thread on a simular issue but it is unclear to me what the > solution is: > http://cxf.547215.n5.nabble.com/STSClient-validateSecurityToken-expects- > RequestSecurityTokenResponseCollection-td5767124.html > > Can anyone help me with this issue? I prefer not to make any changes to the > STS WSDL. > > Thanks, > > Matt DeFazio > > > > > > -- > View this message in context: http://cxf.547215.n5.nabble. > com/Configure-STSClient-to-use-RequestSecurityTokenResponse-tp5782676.html > Sent from the cxf-user mailing list archive at Nabble.com. > -- Colm O hEigeartaigh Talend Community Coder http://coders.talend.com
