FaultExceptions thrown from UserNamePasswordValidators do not get serialised when using BasicHttpBinding
See original GitHub issueHello,
Last year I submitted #676, I’ve just upgraded our CoreWCF references to bring in the change, but unfortunately in my case it is still present, at least for BasicHttpBindings. The unit test which the PR for was validated against covered WSHttpBidnings.
The root cause is the TransportSecurityBindingElement.BuildServiceDispatcherCore
builds a SecurityServiceDispatcher
and does not set SendUnsecuredFaults
to true.
This causes error responses to get lost, and the underlying connection is unexpectedly aborted for the client.
The SecurityServiceDispatcher
is marked as internal and I can’t see an obvious way to programmatically set the desired property to true.
In the mean time I’m going to have to revert back and continue using my exception catching middleware which “fakes” a correct WCF error response.
Issue Analytics
- State:
- Created 7 months ago
- Comments:6
Top GitHub Comments
@g7ed6e With the build released today, 1.5.0-alpha.18, I’m finally getting the SOAP error response for authentication errors in my migrated application, thank you so much!
@marlon-tucker thank you for feedback. I’m closing the issue then as #1083 resolved it.