If credentials are sent in standard way, for example SOAP UsernameToken or HTTP basic - you can use existing CXF interceptors to extract user name/ password for further LDAP authentication.
http://www.jroller.com/gmazza/entry/cxf_usernametoken_profile http://henning.fjas.no/blog/2010/03/25/basic-authentication-cxf-tips-and-tricks-part-1/ Cheers, Andrei. > -----Original Message----- > From: jbright [mailto:[email protected]] > Sent: Freitag, 30. November 2012 17:01 > To: [email protected] > Subject: Re: Response not coming in SOAPUI > > It worked as I found the message was not set correct in the code. > > Yes we do throw exception and a custom error message is created. > > I extended AbstractSoapInterceptor as our requirement is to authenticate > using LDAP. > > > > Thanks > John > > On Nov 30, 2012, at 7:14 PM, "Andrei Shakirin [via CXF]" <ml- > [email protected]> wrote: > > > I think more appropriate solution will be throwing the exception instead > aborting interceptor chain in case of failed authentication. > > It can be SoapFault exception (like in WSS4JInIntercepor), you will be able > to set fault code, message and details as you want. > > > > I am not sure why your solution doesn't work, seems that chain is aborted > and response is hasn't been put in the message. > > > > May I ask what is the reason of introducing own authentication interceptor > and not using CXF ones? > > CXF supports a lot of authentication schemas out of the box: HTTP basic, > UsernameToken, SAML, Kerberos, etc. > > > > Cheers, > > Andrei. > > > > > > > -----Original Message----- > > > From: jbright [mailto:[hidden email]] > > > Sent: Freitag, 30. November 2012 10:50 > > > To: [hidden email] > > > Subject: Response not coming in SOAPUI > > > > > > I've introduced interceptor to read the request SoapMessage and do > > > authentication. > > > > > > If unauthenticated, I do abort() the interceptor chain and sending > > > an error message in the response. > > > > > > The problem is the response message is built using the SOAPMessage > > > of SAAJ. > > > ... > > > > > > When I make the request from the SOAPUI, the response is not coming > > > back in SOAPUI. > > > > > > But when I check the log, the response is there in the payload. > > > > > > I've used the SAAJOutInterceptor in the config file... > > > > > > <jaxws:outInterceptors> > > > <ref bean="saajOutInterceptor" /> > > > <ref bean="logOutbound" /> > > > </jaxws:outInterceptors> > > > > > > If I remove the SAAJOutInterceptor from the config file, the > > > response is not at all coming... > > > > > > > > > > > > -- > > > View this message in context: > > > http://cxf.547215.n5.nabble.com/Response- > > > not-coming-in-SOAPUI-tp5719484.html > > > Sent from the cxf-user mailing list archive at Nabble.com. > > > > > > If you reply to this email, your message will be added to the discussion > below: > > http://cxf.547215.n5.nabble.com/Response-not-coming-in-SOAPUI- > tp571948 > > 4p5719497.html To unsubscribe from Response not coming in SOAPUI, > > click here. > > NAML > > > > > -- > View this message in context: http://cxf.547215.n5.nabble.com/Response- > not-coming-in-SOAPUI-tp5719484p5719511.html > Sent from the cxf-user mailing list archive at Nabble.com.
