axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "AravindPS (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (RAMPART-380) Axis2/Rampart Secure Conversation Inter-operability With .NET client
Date Fri, 06 Jul 2012 11:39:34 GMT

     [ https://issues.apache.org/jira/browse/RAMPART-380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

AravindPS updated RAMPART-380:
------------------------------

    Attachment: Axis2_Log_Axis2-1.6.0_Rampart-1.6.0.txt

.Net inter operability
                
> Axis2/Rampart Secure Conversation Inter-operability With .NET client
> --------------------------------------------------------------------
>
>                 Key: RAMPART-380
>                 URL: https://issues.apache.org/jira/browse/RAMPART-380
>             Project: Rampart
>          Issue Type: Bug
>          Components: rampart-core, rampart-integration, rampart-policy
>    Affects Versions: 1.6.0
>         Environment: Windows 7 Enterprise Service pack 1, jboss-5.1.0.GA, axis2-1.5.5
(exploded war), rampart-1.6.0
>            Reporter: AravindPS
>              Labels: axis21.5.5, rampart1.6.0
>         Attachments: Axis2_Log_Axis2-1.6.0_Rampart-1.6.0.txt, SecureConv.NetInterOperabilityIssue.zip
>
>
>   We have built web service using Axis2 1.5.5 / Rampart 1.6.0. We are supporting the
WS-Security authentication mechanisms. We have a service which implements the ws-secure conversation
authentication. We are trying to test the inter-operability of this service with .Net client.

>   We are facing some issues regarding this. 
>   We have taken help of microsoft support and have tweaked the policy at the .Net side
to sync with the ws-secure conversation policy at the rampart server side. But even after
this, we are getting the error. Let me know if inter-operability with .Net is possible and
if yes let us know how to solve this issue.
>   I have attached the axis2 logs. 
>   I suspect the issue is that the .Net client is not able to consume the response sent
from STS (sct-issuer-config) (the RSTR action) because of policy mismatch and also the fact
that we have not specified any policy to be adhered to by the response action RSTR. Can we
give a policy for "sct-issuer-config"?
>   I have attached relevant log files.
>   Let me know if you need further details.
> Aravind

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org


Mime
View raw message