HongmeiG https://docs.microsoft.com/archive/blogs/hongmeig1/feed.xml Sun, 12 Apr 2015 19:37:31 GMT en-US hourly 1 WCF: NotSupportedException: The SSL settings for the service 'SslRequireCert' does not match those of the IIS 'Ssl'. https://docs.microsoft.com/archive/blogs/hongmeig1/wcf-notsupportedexception-the-ssl-settings-for-the-service-sslrequirecert-does-not-match-those-of-the-iis-ssl Thu, 23 May 2013 22:33:00 GMT https://blogs.msdn.microsoft.com/hongmeig1/2013/05/23/wcf-notsupportedexception-the-ssl-settings-for-the-service-sslrequirecert-does-not-match-those-of-the-iis-ssl/ When you are using WCF with client certificate over SSL in web hosted case, you might hit an exception like the following:

[NotSupportedException: The SSL settings for the service 'SslRequireCert' does not match those of the IIS 'Ssl'.]

System.ServiceModel.Activation.HostedAspNetEnvironment.ValidateHttpsSettings(String virtualPath, Nullable`1& requireClientCertificate) +117347 System.ServiceModel.Channels.HttpsChannelListener.ApplyHostedContext(String virtualPath, Boolean isMetadataListener) +97 System.ServiceModel.Activation.HostedAspNetEnvironment.ApplyHostedContext(TransportChannelListener listener, BindingContext context) +84 System.ServiceModel.Channels.HttpsTransportBindingElement.BuildChannelListener(BindingContext context) +93 System.ServiceModel.Channels.BindingContext.BuildInnerChannelListener() +63 System.ServiceModel.Channels.MessageEncodingBindingElement.InternalBuildChannelListener(BindingContext context) +67

…

Why?

The exception text is actually quite informative in this case. The IIS configuration is telling you that it is only SSL with any cert but the WCF is configured with client certificate over SSL. Your configuration section could look like the following.

            <security mode="Transport">
                <transport clientCredentialType="Certificate" />
            </security>

 

How to fix that?

Now go to your inetmgr, navigate to the virtual directory, and click on the SSL Setting, and make sure “Require” certificate is selected instead of “Ignore”. Now, if you have a sub directory under the v-dir, make sure you click on any sub directory as well and double check your SSL setting to require certificate.

Alternatively, open the master iis Host config file at C:\Windows\System32\inetsrv\config\applicationHost.config, and then search for “Default Web Site/MyVdir”. And see if it only contains “ssl”, like the following:

   <location path="Default Web Site/MyVdir">
        <system.webServer>
            <security>
                <access sslFlags="Ssl" />
            </security>
        </system.webServer>
    </location>

To fix this, just add additional sslFlags to look like the following.

  <location path="Default Web Site/MyVdir">
        <system.webServer>
            <security>
               <access sslFlags="Ssl, SslNegotiateCert, SslRequireCert" />
            </security>
        </system.webServer>
    </location>

Now make sure the changes are saved and do an iisreset before trying to hit the server again.

]]> Learning SignalR: Unable to get property 'client' of undefined or null reference https://docs.microsoft.com/archive/blogs/hongmeig1/learning-signalr-unable-to-get-property-client-of-undefined-or-null-reference Thu, 18 Apr 2013 11:52:00 GMT https://blogs.msdn.microsoft.com/hongmeig1/2013/04/18/learning-signalr-unable-to-get-property-client-of-undefined-or-null-reference/ One of the most common exceptions you will hit when you first started with a SignalR chat program could look like the following:

Unhandled exception at line 78, column 13 in https://localhost:53632/home/chat

0x800a138f - JavaScript runtime error: Unable to get property 'client' of undefined or null reference

Why?

This is mostly like caused by the fact that your Hub class name and your javascript probably does not match. It is case sensitive. By default, SignalR runtime uses camel casing of the Hub class name.

For example, if your hub class looks like the following:  

   1: public class MyChatHub : Hub 
   2: { 
   3:     public void Send(string name, string message) 
   4:     { 
   5:         Clients.All.broadcastMyMessage(name, message); 
   6:     } 
   7: }

And the proxy referenced in your HtmlPage1.html might look like the following:

   1: // Declare a proxy to reference the hub.  
   2: var chat = $.connection.MyChatHub;

Now this does not work since camel casing means that you need to use "myChatHub" instead. so to fix it, you can modify your client side page to use the correct casing. 

   1: // Declare a proxy to reference the hub.  
   2: var chat = $.connection.myChatHub;

Now if you would like to override this default behavior, you could add the HubName attribute to your MyChatHub class. SignalR runtime will use your name as it is, in whatever casing you like, as the name of the proxy. 

   1: [HubName("MyChatHub")] 
   2: public class MyChatHub : Hub 
   3: { 
   4:     // omit the method here for simplicity 
   5: }

 

Hope this helps.

]]> How to customize parameter binding https://docs.microsoft.com/archive/blogs/hongmeig1/how-to-customize-parameter-binding Fri, 28 Sep 2012 11:47:00 GMT https://blogs.msdn.microsoft.com/hongmeig1/2012/09/28/how-to-customize-parameter-binding/ Web API provides some great out of box experience with parameter binding. It also provides some powerful extensibility points to allow you customize that binding process. For example, you can bind multiple parameters from uri. However, it can only bind one parameter from request content by default. If you try to mark multiple parameters with [FromBody] attribute, you will get an error. The other good example is sometimes people might want to bind a parameter from some other source instead of request. There are also occasions where some parameter might come from either request uri or request body. For all those situations,  a custom parameter binding will be your friend.

Scenario 1: How to bind a parameter not coming from request

Say you have a controller that will take an IPrincipal as an parameter. The IPrincipal is not coming from request. So your action looks like the following.

Code Snippet
  1.        [HttpGet]
  2.         public HttpResponseMessage BindPrincipal(IPrincipal principal)
  3.         {
  4.             return Request.CreateResponse(System.Net.HttpStatusCode.Accepted,
  5.                 String.Format("BindPrincipal with Principal name {0}.", principal.Identity.Name));
  6.         }

 Here is your custom parameter binding to bind a custom principal to the IPrincipal parameter. 

Code Snippet
  1.     /// <summary>
  2.     /// A Custom HttpParameterBinding to bind a complex type, e.g. IPrincipal, which is not coming from request
  3.     /// </summary>
  4.     public class PrincipalParameterBinding : HttpParameterBinding
  5.     {
  6.         public PrincipalParameterBinding(HttpParameterDescriptor desc)
  7.             : base(desc)
  8.         {
  9.         }
  10.  
  11.         public override Task ExecuteBindingAsync(ModelMetadataProvider metadataProvider, HttpActionContext actionContext, CancellationToken cancellationToken)
  12.         {
  13.             // Set the binding result here
  14.             SetValue(actionContext, new GenericPrincipal(new GenericIdentity("MyIdentity"), new string[]{"myrole"}));
  15.  
  16.             // now, we can return a completed task with no result
  17.             TaskCompletionSource<AsyncVoid> tcs = new TaskCompletionSource<AsyncVoid>();
  18.             tcs.SetResult(default(AsyncVoid));
  19.             return tcs.Task;
  20.         }
  21.  
  22.         private struct AsyncVoid
  23.         {
  24.         }
  25.     }

 

Scenario 2:  How to bind a complex type either from body or from uri

 Sometimes, server might need to handle different type of requests. Some requests have information stored in the request Uri, and others have them stored in the request body. Here is how you can write one action to handle both types of requests. Your action code might look like the following:

Code Snippet
  1.         [HttpGet]
  2.         [HttpPost]
  3.         public HttpResponseMessage BindCustomComplexTypeFromUriOrBody(TestItem item)
  4.         {
  5.             return Request.CreateResponse(System.Net.HttpStatusCode.Accepted,
  6.                 String.Format("BindCustomComplexTypeFromUriOrBody returns item.Name = {0}.", item.Name));
  7.         }

 Your custom parameter binding can delegate the work to either FromUri or FromBody.

Code Snippet
  1. /// <summary>
  2. /// A Custom HttpParameterBinding to bind a complex type either from request body or uri
  3. /// </summary>
  4. public class FromUriOrBodyParameterBinding : HttpParameterBinding
  5. {
  6.     HttpParameterBinding _defaultUriBinding;
  7.     HttpParameterBinding _defaultFormatterBinding;
  8.  
  9.     public FromUriOrBodyParameterBinding(HttpParameterDescriptor desc)
  10.         : base(desc)
  11.     {
  12.         _defaultUriBinding = new FromUriAttribute().GetBinding(desc);
  13.         _defaultFormatterBinding = new FromBodyAttribute().GetBinding(desc);
  14.     }
  15.  
  16.     public override Task ExecuteBindingAsync(ModelMetadataProvider metadataProvider, HttpActionContext actionContext, CancellationToken cancellationToken)
  17.     {
  18.         if (actionContext.Request.Content != null && actionContext.Request.Content.Headers.ContentLength > 0)
  19.         {
  20.             // we have something from the body, try that first
  21.             return _defaultFormatterBinding.ExecuteBindingAsync(metadataProvider, actionContext, cancellationToken);
  22.         }
  23.         else
  24.         {
  25.             // we need to read things from uri
  26.             return _defaultUriBinding.ExecuteBindingAsync(metadataProvider, actionContext, cancellationToken);
  27.         }
  28.     }
  29.  
  30. }

 

Scenario 3: How to bind a parameter with a different property Name

Due to various reasons, the request sometimes contains a different name for a property than the actual property name defined on the server. How do we get those mapped correctly? For example, here is the type definition that its property is named "Name" on the server, but the client wants to send it  using "$Name" instead.

Code Snippet
  1. public class TestItemRenameProperty
  2. {
  3.     [DataMember(Name = "$Name")]
  4.     public string Name { get; set; }
  5. }

Here is how the action could look like.

Code Snippet
  1. [HttpGet]
  2. public HttpResponseMessage BindCustomComplexTypeFromUriWithRenamedProperty(TestItemRenameProperty item)
  3. {
  4.     return Request.CreateResponse(System.Net.HttpStatusCode.Accepted,
  5.         String.Format("BindCustomComplexTypeFromUriWithRenamedProperty item.Name = {0}.", item.Name));
  6. }


Scenario 4: How to bind multiple parameters form a request body

This might be the most common case where you want to use custom parameter bindings. Out of box, one could only bind one parameter from request body. It forces user who want to bind multiple objects having to write a wrapper class to wrap all those parameters. Fortunately, you can also write a custom parameter binding to solve that problem elegantly. Here is how your action might look like, and your first name and last name are coming from request body.  

Code Snippet
  1. [HttpPost]
  2. public HttpResponseMessage PostMultipleParametersFromBody(string firstname, string lastname)
  3. {
  4.     return Request.CreateResponse(System.Net.HttpStatusCode.Accepted,
  5.         String.Format("BindCustomCoPostMultipleParametersFromBodymplexType FristName = {0}, LastName = {1}.", firstname, lastname));
  6. }

Now let us write a parameter binding to map those values from request body to firstname and lastname parameters.

Code Snippet
  1. /// <summary>
  2. /// A Custom HttpParameterBinding to bind multiple parameters from request body
  3. /// </summary>
  4. public class MultipleParameterFromBodyParameterBinding : HttpParameterBinding
  5. {
  6.     private const string MultipleBodyParameters = "MultipleBodyParameters";
  7.  
  8.     public MultipleParameterFromBodyParameterBinding(HttpParameterDescriptor descriptor)
  9.         : base(descriptor)
  10.     {
  11.     }
  12.  
  13.     public override Task ExecuteBindingAsync(ModelMetadataProvider metadataProvider, HttpActionContext actionContext, CancellationToken cancellationToken)
  14.     {
  15.         NameValueCollection col = TryReadBody(actionContext.Request);
  16.  
  17.         if (col == null)
  18.         {
  19.             throw new HttpResponseException(System.Net.HttpStatusCode.BadRequest);
  20.         }
  21.  
  22.         // Set the binding result here
  23.         SetValue(actionContext, col[Descriptor.ParameterName]);
  24.  
  25.         // now, we can return a completed task with no result
  26.         TaskCompletionSource<AsyncVoid> tcs = new TaskCompletionSource<AsyncVoid>();
  27.         tcs.SetResult(default(AsyncVoid));
  28.         return tcs.Task;
  29.     }
  30.  
  31.     NameValueCollection TryReadBody(HttpRequestMessage request)
  32.     {
  33.         object result = null;
  34.         if (!request.Properties.TryGetValue(MultipleBodyParameters, out result))
  35.         {
  36.             // parsing the string like firstname=Hongmei&lastname=Ge
  37.             NameValueCollection collection = new NameValueCollection();
  38.             result = request.Content.ReadAsFormDataAsync().Result;
  39.             request.Properties.Add(MultipleBodyParameters, result);
  40.         }
  41.  
  42.         return result as NameValueCollection;
  43.     }
  44.  
  45.     private struct AsyncVoid
  46.     {
  47.     }
  48. }

 

Final step: How to register a custom parameter binding

Now we have all those wonderful custom Parameter Bindings, how do you tell Web API that you want to use them instead of those default ones? Here is how you can do it. 

Code Snippet
  1.             // Register an action to create custom ParameterBinding
  2.             config.ParameterBindingRules.Insert(0, GetCustomParameterBinding);

 

Code Snippet
  1.      public static HttpParameterBinding GetCustomParameterBinding(HttpParameterDescriptor descriptor)
  2.      {
  3.          if (descriptor.ParameterType == typeof(IPrincipal))
  4.          {
  5.              return new PrincipalParameterBinding(descriptor);
  6.          }
  7.          else if ( descriptor.ParameterType == typeof(TestItem))
  8.          {
  9.              return new FromUriOrBodyParameterBinding(descriptor);
  10.          }
  11.          else if (descriptor.ParameterType == typeof(TestItemRenameProperty))
  12.          {
  13.              return new CustomModelBinderWithPropertyName(descriptor);
  14.          }
  15.          else if ( descriptor.ParameterType == typeof(string) )
  16.          {
  17.              return new MultipleParameterFromBodyParameterBinding(descriptor);
  18.          }
  19.          
  20.          // any other types, let the default parameter binding handle
  21.          return null;
  22.      }

 

To summarize, custom parameter binding is a powerful extensibility point which allows users to take full control of the parameter binding process. To learn more details, you can download the sample code from our aspnet codeplex site at https://aspnet.codeplex.com/SourceControl/changeset/66590b705e5b.

Happy coding with ASPNET Web API!

]]> Great Hiring event for Microsoft Server and Tools https://docs.microsoft.com/archive/blogs/hongmeig1/great-hiring-event-for-microsoft-server-and-tools Mon, 06 Aug 2012 10:08:18 GMT https://blogs.msdn.microsoft.com/hongmeig1/2012/08/06/great-hiring-event-for-microsoft-server-and-tools/ For more details, please visit https://stbjobs.com/.

]]> How to retrieve all the filters that applies to one particular action in Web API https://docs.microsoft.com/archive/blogs/hongmeig1/how-to-retrieve-all-the-filters-that-applies-to-one-particular-action-in-web-api Mon, 09 Jul 2012 23:07:00 GMT https://blogs.msdn.microsoft.com/hongmeig1/2012/07/09/how-to-retrieve-all-the-filters-that-applies-to-one-particular-action-in-web-api/ Sometimes you want to retrieve all the filters that one action supports, and you can do that via the following code snippet. Hope this helps.

Code Snippet
  1.          Collection<FilterInfo> filterInfoCollection = action.GetFilterPipeline(); // here action is action descriptor
  2.  
  3.          foreach (FilterInfo filterInfo in filterInfoCollection)
  4.          {
  5.              if (filterInfo.Instance is MyQueryableAttribute)
  6.              {
  7.                   supportQueryable = true;
  8.                   break;
  9.              }
  10.          }
]]> How to access the Client's IP address in Web API https://docs.microsoft.com/archive/blogs/hongmeig1/how-to-access-the-clients-ip-address-in-web-api Mon, 09 Jul 2012 10:07:00 GMT https://blogs.msdn.microsoft.com/hongmeig1/2012/07/09/how-to-access-the-clients-ip-address-in-web-api/ For web hosted, you can access your client address via the following:

Code Snippet
  1.             string clientAddress = HttpContext.Current.Request.UserHostAddress;

For self hosted, you can access your client address via the following:

Code Snippet
  1.             object property;
  2.             Request.Properties.TryGetValue(typeof(RemoteEndpointMessageProperty).FullName, out property);
  3.             RemoteEndpointMessageProperty remoteProperty = property as RemoteEndpointMessageProperty;

Hope this helps. 

]]> How to write a custom parameter binding to construct an object either from body or from Uri's query https://docs.microsoft.com/archive/blogs/hongmeig1/how-to-write-a-custom-parameter-binding-to-construct-an-object-either-from-body-or-from-uris-query Fri, 11 May 2012 15:16:25 GMT https://blogs.msdn.microsoft.com/hongmeig1/2012/05/11/how-to-write-a-custom-parameter-binding-to-construct-an-object-either-from-body-or-from-uris-query/ Mike has wrote this really good blog on writing a custom HttpParameterBinding at

https://blogs.msdn.com/b/jmstall/archive/2012/05/11/webapi-parameter-binding-under-the-hood.aspx

My blog just want to add a little bit complex example where you might want to have an action which looks like the following:

Code Snippet
  1. public class HomeController : ApiController
  2. {
  3.     [HttpGet]
  4.     [HttpPost]
  5.     public HttpResponseMessage BindCustomComplexTypeFromUriOrBody(TestItem item)
  6.     {
  7.         return new HttpResponseMessage
  8.         {
  9.             Content = new StringContent(String.Format("BindCustomComplexType item.Name = {0}.", item.Name))
  10.         };
  11.     }
  12. }
  13.  
  14. public class TestItem
  15. {
  16.     public string Name { get; set; }
  17. }

Then the TestItem object can sometimes come from query like /?Name=Hongmei or coming from body. {Name:Hongmei}. It will be easy to write a custom parameter binding to do that.

Step 1: Write a custom FromUriOrFromBodyParameterBinding

Code Snippet
  1. public class FromUriOrBodyParameterBinding : HttpParameterBinding
  2.     {
  3.         HttpParameterBinding _defaultUriBinding;
  4.         HttpParameterBinding _defaultFormatterBinding;
  5.  
  6.         public FromUriOrBodyParameterBinding(HttpParameterDescriptor desc)
  7.             : base(desc)
  8.         {
  9.             _defaultUriBinding = new FromUriAttribute().GetBinding(desc);
  10.             _defaultFormatterBinding = new FromBodyAttribute().GetBinding(desc);
  11.         }
  12.  
  13.         public override Task ExecuteBindingAsync(ModelMetadataProvider metadataProvider, HttpActionContext actionContext, CancellationToken cancellationToken)
  14.         {
  15.             if (actionContext.Request.Content != null )
  16.             {
  17.                 // we have something from the body, try that first
  18.                 return _defaultFormatterBinding.ExecuteBindingAsync(metadataProvider, actionContext, cancellationToken);
  19.             }
  20.             else
  21.             {
  22.                 // we need to read things from uri
  23.                 return _defaultUriBinding.ExecuteBindingAsync(metadataProvider, actionContext, cancellationToken);
  24.             }
  25.         }
  26.  
  27.     }

 

Step 2:  Wire the FromUriOrFromBodyParameterBinding to the configuration

Code Snippet
  1. public static HttpParameterBinding GetCustomParameterBinding(HttpParameterDescriptor descriptor)
  2.         {
  3.             if ( descriptor.ParameterType == typeof(TestItem))
  4.             {
  5.                 return new FromUriOrBodyParameterBinding(descriptor);
  6.             }
  7.  
  8.             // any other types, let the default parameter binding handle
  9.             return null;
  10.         }
Code Snippet
  1. config.ParameterBindingRules.Insert(0, GetCustomParameterBinding);

 

 

]]> How to access ClientCertificate in a host agnostic manner https://docs.microsoft.com/archive/blogs/hongmeig1/how-to-access-clientcertificate-in-a-host-agnostic-manner Fri, 11 May 2012 14:54:00 GMT https://blogs.msdn.microsoft.com/hongmeig1/2012/05/11/how-to-access-clientcertificate-in-a-host-agnostic-manner/  When you choose to use Client Certificate as your client credential over SSL, you want to retrieve the x509 Certificate on the server side to do authorization. It is very simple with the latest Web API bits. If you have access to the request message anywhere in the pipeline, such as message handler, action filter or action. you can simply call the extension method shown below. Please be careful that the GetClientCertificate method might return null if the client does not send an valid certificate.

Now getting the client certificate is easy, but how to set it up correctly on self host and web host is not that easy. The following instructions walk you through the process step by step.

Web Host

Step 1: go to the IIS manager, SSL setting, check require client certificate

Step 2: register a custom message handler and verify that the client certificate is something you expect.

Code Snippet
  1. public class CustomCertificateMessageHandler : DelegatingHandler
  2.     {
  3.         protected override Task<HttpResponseMessage> SendAsync(HttpRequestMessage request, CancellationToken cancellationToken)
  4.         {
  5.             X509Certificate cert = request.GetClientCertificate();
  6.             if (cert != null)
  7.             {
  8.                 if (cert.Subject.Contains("Some Name you are expecting"))
  9.                 {
  10.                     Thread.CurrentPrincipal = new GenericPrincipal(new GenericIdentity(cert.Subject), new[] { "Administrators" });
  11.                 }
  12.             }
  13.  
  14.             return base.SendAsync(request, cancellationToken);
  15.         }
  16.     }

Step 3: register the custom message handler.

Code Snippet
  1. // Register a message to turn the client cert to a admin role
  2.             GlobalConfiguration.Configuration.MessageHandlers.Add(new CustomCertificateMessageHandler());

 

Step 4: Write a RequireAdminAttribute

Code Snippet
  1. public class RequireAdminAttribute : AuthorizationFilterAttribute
  2.     {
  3.         public override void OnAuthorization(HttpActionContext context)
  4.         {
  5.             // do authorization based on the principle.
  6.             IPrincipal principal = Thread.CurrentPrincipal;
  7.             if (principal == null || !principal.IsInRole("Administrators"))
  8.             {
  9.                 context.Response = new HttpResponseMessage(HttpStatusCode.Unauthorized);
  10.             }
  11.         }
  12.     }

Step 5: Add the RequireAdminAttribute to the action.

Code Snippet
  1. public class HomeController : ApiController
  2.     {
  3.         [RequireAdmin]
  4.         public HttpResponseMessage Get()
  5.         {
  6.             return new HttpResponseMessage(HttpStatusCode.OK)
  7.             {
  8.                 Content = new StringContent("Default User")
  9.             };
  10.         }
  11.  
  12.         public HttpResponseMessage Post()
  13.         {
  14.             return new HttpResponseMessage(HttpStatusCode.OK)
  15.             {
  16.                 Content = new StringContent("User Posted")
  17.             };
  18.         }
  19.     }

Now your GET action can only be accessed with the administrators.

Self Host

Step 1: Tell the WCF transport, I want to client to send certificate over SSL.

Code Snippet
  1.             // client cert
  2.             config.ClientCredentialType = HttpClientCredentialType.Certificate;

Step 2: Write some client code to pick a certificate to send

Code Snippet
  1.                 WebRequestHandler handler = new WebRequestHandler();
  2.                 handler.ClientCertificateOptions = ClientCertificateOption.Manual; // this would pick from the Current user store
  3.                 handler.ClientCertificates.Add(GetClientCertificate());
  4.                 handler.UseDefaultCredentials = true;
  5.                 HttpClient client = new HttpClient(handler);

Implement the GetClientCertificate to retrieve a certificate programmatically.

Then repeat step 2-5 from the web host section to complete the experience.

Hope this helps.  

 

]]> How to support multiple authentication in self host https://docs.microsoft.com/archive/blogs/hongmeig1/how-to-support-multiple-authentication-in-self-host Fri, 11 May 2012 14:24:50 GMT https://blogs.msdn.microsoft.com/hongmeig1/2012/05/11/how-to-support-multiple-authentication-in-self-host/ Since we build web api self host story on top of WCF HttpTransportBindingElement, the multiple authentication is not support on WCF for 4.0. Here is the exception you will get if you tried to set the authentication scheme on httptransport binding element.

"System.ArgumentException: The 'Negotiate, Anonymous' authentication scheme has been specified on the HTTP factory. However, the factory only supports specification of exactly one authentication scheme.  Valid authentication schemes are Digest, Negotiate, NTLM, Basic, or Anonymous."

The good news is that this has been fixed in .NET framework 4.5 Beta. This is the link https://msdn.microsoft.com/en-us/library/ms171868(v=vs.110).aspx#windows_communication_foundation.

"Ability to support multiple authentication modes on a single WCF endpoint when using the HTTP transport and transport security. "

 So with that fix in mind, web api now provides an extensibility point for people to set the authentication schemes.

 Step 1: Derive from HttpSelfHostConfiguration, and register an action to modify TransportBindingElement, and modify the authentication scheme in the action.

Code Snippet
  1. class MultipleAuthenticationHttpConfiguration : HttpSelfHostConfiguration
  2.         {
  3.             public MultipleAuthenticationHttpConfiguration(string baseAddress)
  4.                 : base(baseAddress)
  5.             {
  6.             }
  7.  
  8.             protected override BindingParameterCollection OnConfigureBinding(HttpBinding httpBinding)
  9.             {
  10.                 httpBinding.ConfigureTransportBindingElement = new Action<HttpTransportBindingElement>(ConfigureTransportBindingElement);
  11.                 return base.OnConfigureBinding(httpBinding);
  12.             }
  13.  
  14.             void ConfigureTransportBindingElement(HttpTransportBindingElement bindingElement)
  15.             {
  16.                 // uncomment the following line if running on 4.5
  17.                 // bindingElement.AuthenticationScheme = AuthenticationSchemes.Negotiate | AuthenticationSchemes.Anonymous;
  18.                 bindingElement.AuthenticationScheme = AuthenticationSchemes.Negotiate;
  19.             }
  20.         }
 

Step 2: use the derived the configuration object instead

Code Snippet
  1. var config = new MultipleAuthenticationHttpConfiguration(Program.BaseAddress);
  2.                 config.Routes.MapHttpRoute("Default", "{controller}", new { controller = "Sample" });
  3.  
  4.                 SetupConfig(config);
  5.  
  6.                 server = new HttpSelfHostServer(config);
  7.                 server.OpenAsync().Wait();
  8.                 Console.WriteLine("Service listening at: " + Program.BaseAddress);
]]> How to access HTTPContext from within your Web API action https://docs.microsoft.com/archive/blogs/hongmeig1/how-to-access-httpcontext-from-within-your-web-api-action Tue, 28 Feb 2012 22:01:20 GMT https://blogs.msdn.microsoft.com/hongmeig1/2012/02/28/how-to-access-httpcontext-from-within-your-web-api-action/ Within a Web API action, you can easily access the HttpContext via the HttpContext.Current thread static. Alternatively, you can also retrieve the context from one of the properties in the Request message.

Code Snippet
  1. HttpContext context;
  2. Request.Properties.TryGetValue<HttpContext>("MS_HttpContext", out context);

Hope this helps.

]]>