eclipse-ee4j / eclipse-ee4j/metro-wsit
Incomplete implementation of BaseSTSImpl
- Dominant language
- Java
- Stars
- 6
- Forks
- 21
- Avg merge
- 10h 2m
- Merged PRs (30d)
- 1
Description
com.sun.xml.ws.security.trust.sts.BaseSTSImpl.cancel(STSConfiguration, String, WSTrustElementFactory, BaseSTSRequest) is currently implemented to return null, rather than making a call to com.sun.xml.ws.api.security.trust.WSTrustContract.cancel(K, IssuedTokenContext, Map). This causes the service to respond with HTTP 202 rather than a fault code indicating that the operation is not implemented.
It would be better to hook the two functions together so that a fault is raised, or so that a WS Trust contract implementation that did provide a cancel operation could be implemented.
#### Affected Versions
[2.1]
Source: [https://github.com/javaee/metro-wsit/issues/1561](https://github.com/javaee/metro-wsit/issues/1561)
Author: glassfishrobot
Contributor guide
Research direction
Start by reading BaseSTSImpl.cancel(STSConfiguration, String, WSTrustElementFactory, BaseSTSRequest) and the WSTrustContract.cancel(K, IssuedTokenContext, Map) contract named in the issue. Trace how the cancel request currently produces HTTP 202, then verify that the completed implementation delegates to the contract or raises the appropriate fault instead.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100