eclipse-ee4j / eclipse-ee4j/metro-wsit

Error when using 2 .NET services with same STS in Java client

Open
#331 0 comments 0 reactions 0 assignees View on GitHub
Component: trust ERR: Assignee interoperability metro2_1-waived metro2_2-waived metro2_3-exclude Priority: Major token_request Type: Bug
Dominant language
Java
Stars
6
Forks
21
Avg merge
10h 2m
Merged PRs (30d)
1

Description

Java client using 2 services with same STS.

Calling first Service with no error. Calling second Service shows following error in STS:

RequestFailed: TrustNamespace=[http://docs.oasis-open.org/ws-sx/ws-trust/200512](http://docs.oasis-open.org/ws-sx/ws-trust/200512), Action=[http://docs.oasis-open.org/ws-sx/ws-trust/200512/RST/Issue](http://docs.oasis-open.org/ws-sx/ws-trust/200512/RST/Issue), Exception=System.Xml.XmlException: End element 'AppliesTo' from namespace 'http://schemas.xmlsoap.org/ws/2004/09/policy' expected. Found element 'ns9:Identity' from namespace 'http://schemas.xmlsoap.org/ws/2006/02/addressingidentity'. Line 1, position 1113.

Only difference in request xml is in its body with:

[http://myserver/MyService2/Service2.svc](http://myserver/MyService2/Service2.svc)

in correct request, versus:

[http://myserver/MyService/Service1.svc](http://myserver/MyService/Service1.svc)

(base64 service certificate)

in wrong request.

If I change the order of service calls, it's always the second call that gives this same error, no matter what the second service is.
#### Environment
Java 1.5 client with Metro 2.1-10/04/2010 snapshot, .NET 4.0 Service, .NET 4.0 STS
#### Affected Versions
[2.1]

Source: [https://github.com/javaee/metro-wsit/issues/1514](https://github.com/javaee/metro-wsit/issues/1514)
Author: glassfishrobot

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.