-
Notifications
You must be signed in to change notification settings - Fork 558
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
BasicHttpMessageSecurity #2211
Comments
@LEsperanca please refer to 2.0 release notes:
At this point we don't have a plan to support message security due to lack of dependent functionalities in |
How can we help? |
I need to have or emulate BasicHttpMessageSecurity in a .net core service and i don't know how... @hugoterelle |
@zhenlan my question was for you. I could help improve your library if needed. @LEsperanca
And then, I created a channel factory (used by Autofac)
|
@hugoterelle I'm not sure how to actually use the ChannelFactory you've created, can you tell me how I inject this into the WCF service so it uses the correct channelfactory? |
@nickcoad builder.Register(c => CreateSecuredChannel("myurl", "myuser", "mypassword")).SingleInstance(); Then, you just need to inject your IMySoapService to use it. And for the UseWcfSafeRelease used by Autofac, just refer to the issue I raised on the Autofac github |
Any ETA on this issue? This is important feature to support for a lot of WCF service migration projects for us. |
@hugoterelle Thank you for your code. I managed to get Basic Auth Message level security working using your code. |
@hugoterelle Your code works for me. Thank you very much! Do you wanna make a nuget package till MS do it properly? @nickcoad FYI You don't have to use Autofac. You able to use any DI or simply:
|
@hugoterelle Thank you very much for your work. It saved my day. |
This is not really a issue, when will BasicHttpMessageSecurity be supported by .net core 2.0?
The text was updated successfully, but these errors were encountered: