eclipse-ee4j / eclipse-ee4j/metro-wsit
metro client fails against the service running on SOA and using SAML Token With No MTOM
- Dominant language
- Java
- Stars
- 6
- Forks
- 21
- Avg merge
- 10h 2m
- Merged PRs (30d)
- 1
Description
SAML Scenario failing with metro 1.6
Scenario details
==========
Client metro-1.6 ------------> SOA Service
Server endpoint
===============
SOA Proxy Endpoint
===================
[http://ejp5356-vm2.india.sun.com:8001/soa-infra/services/default/SamlTokenWithoutMtomProject!1.0*soa_7c84932d-97ba-4415-9248-e73ba0024afe/Mediator1_ep?WSDL](http://ejp5356-vm2.india.sun.com:8001/soa-infra/services/default/SamlTokenWithoutMtomProject!1.0*soa_7c84932d-97ba-4415-9248-e73ba0024afe/Mediator1_ep?WSDL)
Glassfish Service Endpoint
===========================
[http://ejp5360-vm3.india.sun.com:8080//SamlTokenServiceWithoutMTOM/SamlTokenRpcWithoutMtomService?wsdl](http://ejp5360-vm3.india.sun.com:8080//SamlTokenServiceWithoutMTOM/SamlTokenRpcWithoutMtomService?wsdl)
#### Environment
Operating System: All
Platform: All
#### Affected Versions
[1.6]
Source: [https://github.com/javaee/metro-wsit/issues/1454](https://github.com/javaee/metro-wsit/issues/1454)
Author: glassfishrobot
Contributor guide
Assessment
This issue has not been assessed yet.