eclipse-ee4j / eclipse-ee4j/metro-wsit
Three Interop-wssx s<->s Scenarios are failing on tomcat.
- Dominant language
- Java
- Stars
- 6
- Forks
- 21
- Avg merge
- 10h 2m
- Merged PRs (30d)
- 1
Description
Scenarios
=========
Interop Scenario 1-wssx - Client_SUN STS_SUN Server_SUN
Interop Scenario 2-wssx - Client_SUN STS_SUN Server_SUN
Interop Scenario 3-wssx - Client_SUN STS_SUN Server_SUN
Error Message
=============
WSSPIPE0035: Recieved Exception during IssuedToken Creation.
Soap Message
============
done seeding SecureRandom
Mar 14, 2008 9:13:12 PM com.sun.xml.ws.security.trust.impl.TrustPluginImpl
doMexRequest
SEVERE: WST0017:Could not obtain STS metadata. MEX call to STS
[https://localhost:8181/jaxws-s3-wssx-sts/sts/mex](https://localhost:8181/jaxws-s3-wssx-sts/sts/mex) failed.
Mar 14, 2008 9:13:12 PM com.sun.xml.wss.jaxws.impl.SecurityClientPipe
invokeTrustPlugin
SEVERE: WSSPIPE0035: Recieved Exception during IssuedToken Creation.
com.sun.xml.ws.api.security.trust.WSTrustException: WST0017:Could not obtain STS
metadata. MEX call to STS [https://localhost:8181/jaxws-s3-wssx-sts/sts/mex](https://localhost:8181/jaxws-s3-wssx-sts/sts/mex) failed.
at
com.sun.xml.ws.security.trust.impl.TrustPluginImpl.doMexRequest(TrustPluginImpl.java:528)
at
com.sun.xml.ws.security.trust.impl.TrustPluginImpl.invokeRST(TrustPluginImpl.java:400)
at
com.sun.xml.ws.security.trust.impl.TrustPluginImpl.process(TrustPluginImpl.java:174)
at
com.sun.xml.ws.security.trust.impl.client.STSIssuedTokenProviderImpl.issue(STSIssuedTokenProviderImpl.java:53)
at
com.sun.xml.ws.api.security.trust.client.IssuedTokenManager.getIssuedToken(IssuedTokenManager.java:79)
at
com.sun.xml.wss.jaxws.impl.SecurityClientPipe.invokeTrustPlugin(SecurityClientPipe.java:484)
at
com.sun.xml.wss.jaxws.impl.SecurityClientPipe.process(SecurityClientPipe.java:178)
at com.sun.xml.ws.api.pipe.helper.PipeAdapter.processRequest(PipeAdapter.java:115)
at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:598)
at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:557)
at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:542)
at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:439)
at com.sun.xml.ws.client.Stub.process(Stub.java:248)
at com.sun.xml.ws.client.sei.SEIStub.doProcess(SEIStub.java:135)
at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:109)
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 $Proxy40.ping(Unknown Source)
at simple.client.PingServiceClient.testMain(PingServiceClient.java:46)
at simple.client.PingServiceClient.main(PingServiceClient.java:27)
Caught Exception: WSSPIPE0035: Recieved Exception during IssuedToken Creation.
javax.xml.ws.WebServiceException: WSSPIPE0035: Recieved Exception during
IssuedToken Creation.
at
com.sun.xml.wss.jaxws.impl.SecurityClientPipe.invokeTrustPlugin(SecurityClientPipe.java:493)
at
com.sun.xml.wss.jaxws.impl.SecurityClientPipe.process(SecurityClientPipe.java:178)
at com.sun.xml.ws.api.pipe.helper.PipeAdapter.processRequest(PipeAdapter.java:115)
at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:598)
at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:557)
at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:542)
at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:439)
at com.sun.xml.ws.client.Stub.process(Stub.java:248)
at com.sun.xml.ws.client.sei.SEIStub.doProcess(SEIStub.java:135)
at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:109)
at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:89)
#### Environment
Operating System: All
Platform: All
#### Affected Versions
[1.2]
Source: [https://github.com/javaee/metro-wsit/issues/853](https://github.com/javaee/metro-wsit/issues/853)
Author: glassfishrobot
Contributor guide
Research direction
Start with the three Interop-wssx scenarios and reproduce the MEX failure against the STS endpoint shown in the report. Read TrustPluginImpl.java at doMexRequest (line 528) and SecurityClientPipe.java at invokeTrustPlugin, then verify that the scenarios can obtain STS metadata and complete successfully on Tomcat.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100