[
https://issues.apache.org/jira/browse/RAMPART-380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13407905#comment-13407905
]
AravindPS commented on RAMPART-380:
-----------------------------------
Hi,
We deployed the web service in axis2-1.6.0/Rampart-1.6.0 and ran the same
inter operability test. It is still giving the same issue. I have attached the
axis2 log for this. Let us know if we can get a fix for this. Also, let us know
if we have to "change any policy/provide sts policy" to handle this.
Also, we have the Microsoft ticket still open as of now. We can pass any
information to them if we need to.
Regards,
Aravind
> 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: 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: [email protected]
For additional commands, e-mail: [email protected]
