I wrote a username password validator descendant for validation purposes (basic HTTP binding).
The hassle is after I validate a person towards a lower back carrier I get hold of its identifier that I must use in carrier-class technique. That turns out to be a massive hassle... Until you realize a way to do it ...
Is there some other authorization opportunity that I will now not bypass username/password in approach header or even worse in method's parameters of the carrier?
0 Replies