eclipse-ee4j / eclipse-ee4j/metro-wsit

metro client fails against the service running on SOA and using SAML Token.

Open
#320 0 comments 0 reactions 0 assignees View on GitHub
Component: security ERR: Assignee metro2_1-waived metro2_2-waived metro2_3-exclude metro2_3-waived Priority: Critical Type: Bug
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
===============
[http://ejp5356-vm2.india.sun.com:8001/soa-infra/services/default/SAMLEcho!1.0*soa_a2598a78-4978-40b3-8ba2-d4cf9261ba98/SAMLMediator_ep?WSDL](http://ejp5356-vm2.india.sun.com:8001/soa-infra/services/default/SAMLEcho!1.0*soa_a2598a78-4978-40b3-8ba2-d4cf9261ba98/SAMLMediator_ep?WSDL)

Request/Response Log
====================
INFO: WSP1049: Loaded WSIT configuration from file:
[file:/scratch/aime1/NetBeansProjects/TestSAMLSOA1/build/classes/META-INF/wsit-client.xml](file:/scratch/aime1/NetBeansProjects/TestSAMLSOA1/build/classes/META-INF/wsit-client.xml)
---[HTTP request -
[http://ejp5356-vm2.india.sun.com:8001/soa-infra/services/default/SAMLEcho!1.0*soa_a2598a78-4978-40b3-8ba2-d4cf9261ba98/SAMLMediator_ep]---](http://ejp5356-vm2.india.sun.com:8001/soa-infra/services/default/SAMLEcho!1.0*soa_a2598a78-4978-40b3-8ba2-d4cf9261ba98/SAMLMediator_ep]---)
Content-type:
multipart/related;start="";type="application/xop+xml";boundary="uuid:b8c99c64-092f-4e3f-81e6-24fdcbf96555";start-info="text/xml"
User-agent: JAX-WS RI 2.1.8-hudson-11-
Soapaction: ""
Accept: text/xml, multipart/related, text/html, image/gif, image/jpeg, *; q=.2,
**/**; q=.2
--uuid:b8c99c64-092f-4e3f-81e6-24fdcbf96555
Content-Id:
Content-Type: application/xop+xml;charset=utf-8;type="text/xml"
Content-Transfer-Encoding: binary

2010-07-06T11:56:18Z2010-07-06T12:01:18Zorakeyurn:oasis:names:tc:SAML:1.0:cm:sender-vouchesATTRIBUTE191tYxY3ACP8PP17Mp9qTI4CcJgw=1278417378455

---[HTTP response -
[http://ejp5356-vm2.india.sun.com:8001/soa-infra/services/default/SAMLEcho!1.0*soa_a2598a78-4978-40b3-8ba2-d4cf9261ba98/SAMLMediator_ep](http://ejp5356-vm2.india.sun.com:8001/soa-infra/services/default/SAMLEcho!1.0*soa_a2598a78-4978-40b3-8ba2-d4cf9261ba98/SAMLMediator_ep)

* 500]---
null: HTTP/1.1 500 Internal Server Error
Content-type: text/xml; charset=utf-8
Content-length: 363
X-powered-by: Servlet/2.5 JSP/2.1
Date: Tue, 06 Jul 2010 11:56:19 GMT
X-oracle-dms-ecid: 0000IabbI753Z7e5xbk3yW1C6Z9_003jGF
Soapaction: ""
ns0:FailedCheckFailedCheck
: failure in security
check--------------------
javax.xml.ws.soap.SOAPFaultException: FailedCheck : failure in security check
at
com.sun.xml.ws.fault.SOAP11Fault.getProtocolException(SOAP11Fault.java:189)
at
com.sun.xml.ws.fault.SOAPFaultBuilder.createException(SOAPFaultBuilder.java:122)
at
com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:119)
at
com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:89)
at com.sun.xml.ws.client.sei.SEIStub.invoke(SEIStub.java:118)
at $Proxy37.echo(Unknown Source)
at testsamlsoa1.Main.main(Main.java:26)
BUILD SUCCESSFUL (total time: 3 seconds)

Server Log
==========
####
<[ACTIVE] ExecuteThread: '0' for queue:
'weblogic.kernel.Default (self-tuning)'> <> <> <> <1278418405141>

####
<[ACTIVE] ExecuteThread: '0' for queue:
'weblogic.kernel.Default (self-tuning)'> <> <> <> <1278418405142>

####
<[ACTIVE] ExecuteThread: '0' for queue:
'weblogic.kernel.Default (self-tuning)'> <> <> <> <1278418405143>

####
<[ACTIVE] ExecuteThread: '0' for queue:
'weblogic.kernel.Default (self-tuning)'> <> <> <> <1278418405143>

####
<[ACTIVE] ExecuteThread: '0' for queue:
'weblogic.kernel.Default (self-tuning)'> <> <> <> <1278418405144>

####
<[ACTIVE] ExecuteThread: '0' for queue:
'weblogic.kernel.Default (self-tuning)'> <> <> <> <1278418405171>

#### Environment
Operating System: All
Platform: All
#### Affected Versions
[1.6]

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

Contributor guide

Open the contributing guide

Research direction

Start with the SAML Scenario details and the captured HTTP request/response in the issue, then trace Metro 1.6's SAML and WS-Security interoperability handling. Reproduce the failure against the referenced SOA service and inspect the complete SOAP fault. Done means the Metro client successfully interoperates with that SAML-protected service.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
security
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.