Mailing-List: contact dev-help@cxf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cxf.apache.org
MIME-Version: 1.0
Reply-To: coheigea@apache.org
In-Reply-To: <1398785294847-5743422.post@n5.nabble.com>
References: <1398469734046-5743324.post@n5.nabble.com>
	<CAB8XdGCSjmUkGf=ACH8FG1jdUTktD-exXOAiVnfboc2cRQAomA@mail.gmail.com>
	<1398700986147-5743381.post@n5.nabble.com>
	<CAB8XdGCtNHEKQH_7MBHq+D9GSPQhT4VL9ywg44dfQiNirJPqQQ@mail.gmail.com>
	<1398785294847-5743422.post@n5.nabble.com>
Date: Wed, 30 Apr 2014 15:06:54 +0100
Message-ID: 
 <CAB8XdGCDzPYtVkP1j3y1rAbxje3t6rsP8tqT+sxTs94HXXcLbg@mail.gmail.com>
Subject: Re: Http proxy with STS
From: Colm O hEigeartaigh <coheigea@apache.org>
To: "dev@cxf.apache.org" <dev@cxf.apache.org>
Content-Type: multipart/alternative; boundary=e89a8f3bae6795b17704f8430f24

--e89a8f3bae6795b17704f8430f24
Content-Type: text/plain; charset=UTF-8

Could you try with a http conduit based on the address instead, e.g.?

<http-conf:conduit name="https://localhost:.*">
        <http-conf:client ProxyServer="localhost" ProxyServerPort="3128" />
</http-conf:conduit>

I've tried with this with CXF 3.0.0-SNAPSHOT + the SecureConveration code
does pick up the proxy settings...

Colm.


On Tue, Apr 29, 2014 at 4:28 PM, lotos <splevko@gmail.com> wrote:

> I see timeout too but only for the second request.
>
> First request doesn't use proxy:
>
> 28.04.2014 16:37:01
>
> org.apache.cxf.services.SecurityTokenService.SecurityTokenService.SecurityTokenService
> INFO: Outbound Message
> ---------------------------
> ID: 1
> Address: https://....URL...../account/
> Encoding: UTF-8
> Http-Method: POST
> Content-Type: application/soap+xml;
> action="http://schemas.xmlsoap.org/ws/2005/02/trust/RST/SCT"
> Headers: {Accept=[*/*]}
> Payload: <soap:Envelope
> xmlns:soap="http://www.w3.org/2003/05/soap-envelope
> "><soap:Header>........</wst:RequestSecurityToken></soap:Body></soap:Envelope>
> --------------------------------------
> 28.04.2014 16:37:01
>
> org.apache.cxf.services.SecurityTokenService.SecurityTokenService.SecurityTokenService
> INFO: Inbound Message
> ----------------------------
> ID: 1
> Response-Code: 200
> Encoding: UTF-8
> Content-Type: application/soap+xml; charset=utf-8
> Headers: {Cache-Control=[private], Content-Length=[2329],
> content-type=[application/soap+xml; charset=utf-8], Date=[Mon, 28 Apr 2014
> 20:37:03 GMT], P3P=[CP="NOI ADM DEV PSAi COM NAV OUR OTR STP IND DEM"],
> Server=[Microsoft-IIS/7.5],
> Set-Cookie=[ASP.NET_SessionId=gdst00ndzizcvhbmnmt3pao3; path=/; HttpOnly],
> X-AspNet-Version=[4.0.30319]}
> Payload: <s:Envelope xmlns:s="http://www.w3.org/2003/05/soap-envelope"
> xmlns:a="http://www.w3.org/2005/08/addressing"
> xmlns:u="
> http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd
> ">..........</t:KeySize></t:RequestSecurityTokenResponse></s:Body></s:Envelope>
>
>
> Different variants were tried, here is one of them with xml configuration
>
>     <http-conf:conduit
> name="{...blablabla...}WSHttpBinding_IAccountService.http-conduit">
>         <http-conf:client ProxyServer="localhost" ProxyServerPort="3128" />
>     </http-conf:conduit>
>
>
>
>
> *here is the workaround with features*
>
> <beans xmlns="....">
>
>     <cxf:bus>
>         <cxf:features>
>             <cxf:logging/>
>             <p:policies/>
>         </cxf:features>
>     </cxf:bus>
>
>     <jaxws:client name="{....blablabla....}WSHttpBinding_IAccountService"
> createdFromAPI="true">
>         <jaxws:properties>
>             <entry key="ws-security.signature.properties"
> value="etc/Client_Sign.properties"/>
>             <entry key="ws-security.callback-handler"
> value="demo.wssec.client.UTPasswordCallback" />
>
>             <entry key="ws-security.sts.client">
>                 <bean class="org.apache.cxf.ws.security.trust.STSClient">
>                     <constructor-arg ref="cxf"/>
>                     <property name="features">
>                         <beans:list>
>                             *<bean
> class="demo.wssec.client.ClientProxyFeature"/>*
>                         </beans:list>
>                     </property>
>                 </bean>
>             </entry>
>         </jaxws:properties>
>         <jaxws:features>
>             *<bean class="demo.wssec.client.ClientProxyFeature"/>*
>         </jaxws:features>
>     </jaxws:client>
> </beans>
>
>
>
>
> --
> View this message in context:
> http://cxf.547215.n5.nabble.com/Http-proxy-with-STS-tp5743324p5743422.html
> Sent from the cxf-dev mailing list archive at Nabble.com.
>


-- 
Colm O hEigeartaigh

Talend Community Coder
http://coders.talend.com

--e89a8f3bae6795b17704f8430f24--