You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Kristof Janssens (JIRA)" <ji...@apache.org> on 2013/04/22 08:57:16 UTC
[jira] [Updated] (CXF-4977) Client for .Net WCF using both WS-Trust
and WS-SecureConversation
[ https://issues.apache.org/jira/browse/CXF-4977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kristof Janssens updated CXF-4977:
----------------------------------
Attachment: trust.wsdl
service.wsdl
cxf_client.xml
client_log_net.saz
client_log_cxf.xml
> Client for .Net WCF using both WS-Trust and WS-SecureConversation
> -----------------------------------------------------------------
>
> Key: CXF-4977
> URL: https://issues.apache.org/jira/browse/CXF-4977
> Project: CXF
> Issue Type: Bug
> Components: STS, WS-* Components
> Reporter: Kristof Janssens
> Attachments: client_log_cxf.xml, client_log_net.saz, cxf_client.xml, service.wsdl, trust.wsdl
>
>
> I'm trying to create a client for a .Net WCF service with WS-Trust and WS-SecureConversation.
> The client that I need for this webservice, has to follow the next steps:
> 1. Ask a security token from the STS server
> 2. Receive the security token from the STS server if client is authenticated
> 3. With this security token, ask for a context token from the WCF webservice
> 4. If security token is validated, receive a context token from the WCF webservice
> 5. Start using the WCF webservice using the granted context token.
> The CXF client I've written, doesn't perform steps 3 and 4.
> In the WCF server config, this is the security profile:
> WSSecurity11WSTrust13WSSecureConversation13WSSecurityPolicy12BasicSecurityProfile10
> INfo about the attached files:
> client_log_cxf.xml: logfile from my CXF client
> client_log_net_saz: fiddler logfile from a working .Net client
> cxf_client.xml: my client cxf configfile
> service.wsdl: WSDL for the WCF webservice
> trust.wsdl: WSDL for the STS service
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira