eclipse-ee4j / eclipse-ee4j/metro-wsit
[.net 4.0]Secure conv m->s scenario not working because endpoint is missing
- Dominant language
- Java
- Stars
- 6
- Forks
- 21
- Avg merge
- 10h 2m
- Merged PRs (30d)
- 1
Description
current used endpoint for m->s
[http://INDIGO_HOST/SecurityIndigoMexClient/HostedClient.svc?wsdl](http://INDIGO_HOST/SecurityIndigoMexClient/HostedClient.svc?wsdl)
#### Environment
Operating System: All
Platform: All
#### Affected Versions
[2.0]
Source: [https://github.com/javaee/metro-wsit/issues/1272](https://github.com/javaee/metro-wsit/issues/1272)
Author: glassfishrobot
Contributor guide
Research direction
Start by reviewing the currently referenced HostedClient.svc?wsdl endpoint and the linked Metro WSIT issue 1272. Trace how the secure conversation MEX scenario expects this endpoint to be provided, then verify that the .NET 4.0 scenario can reach the required endpoint and complete successfully.
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
- Needs clarification
- Newbie friendliness
- 25/100