ServiceSecurityContext is null with Castle Windsor WCF Integration Facility

[Khash Sajadi]

I'm trying to use WCF Integration Facility with Castle. So far I have the server and the client working fine. The server is hosted in IIS 7 (with a SVC file with no code behind).

Now I need to know the username of the client. For this I'm doing:

OperationContext oc = OperationContext.Current;
ServiceSecurityContext ssc = oc.ServiceSecurityContext;

But the ssc is null. I guess it has something to do with enabling TransportCredentialOnly on binding, but I don't have any bindings (using .NET 4 Default Bindings - through the Facility).

So the question boils down to:

How can I get the client username in a WCF Integration Facility hosted service on the server side.

[Valeriu Caraulean]

Very rough code snippets, adjust them appropriately...

You should first set your bindings to work properly with Transport credentials:

public static Binding DefaultBinding
{
    get
    {
      return new BasicHttpBinding
      {

         // other binding config

         Security =
         {
           Mode = BasicHttpSecurityMode.TransportCredentialOnly,
           Transport = {ClientCredentialType = HttpClientCredentialType.Windows}
         }

Then you can register explicitly your services in container:

Component
   .For<TService>()
   .ImplementedBy<TServiceImpl>()
   .Named(typeof (TService).Name)
   .LifeStyle.Is(lifestyleType)
   .AsWcfService(CreateServiceModel(typeof(TService), binding));

private static DefaultServiceModel CreateServiceModel (Type serviceType, Binding binding)
{
   return new DefaultServiceModel()
    .Hosted()
    .AddEndpoints(WcfEndpoint
      .ForContract(serviceType)
      .BoundTo(binding));
}

Hope this helps...

--
You received this message because you are subscribed to the Google Groups "Castle Project Development List" group.
To view this discussion on the web visit https://groups.google.com/d/msg/castle-project-devel/-/ym4Pmr4aptkJ.
To post to this group, send email to castle-pro...@googlegroups.com.
To unsubscribe from this group, send email to castle-project-d...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/castle-project-devel?hl=en.

[Khash Sajadi]

Tried that and other varieties. Doesn't make a difference I'm afraid. This is what it looks like now:

https://gist.github.com/1364171

[Valeriu Caraulean]

Hmm, looks OK for me...

Just to be sure, all configuration is done in code? No WCF sections in web.config?

On Mon, Nov 14, 2011 at 4:27 PM, Khash Sajadi <khash....@gmail.com> wrote:

Tried that and other varieties. Doesn't make a difference I'm afraid. This is what it looks like now:

https://gist.github.com/1364171

--
You received this message because you are subscribed to the Google Groups "Castle Project Development List" group.

To view this discussion on the web visit https://groups.google.com/d/msg/castle-project-devel/-/QIBKEfSmMP0J.

[Khash Sajadi]

That's right. It's all code based. Anything specific should be done in the client?

[Valeriu Caraulean]

Nothing fancy in our client code:

  var basicHttpBinding = new BasicHttpBinding(BasicHttpSecurityMode.TransportCredentialOnly)

That's enough for us to have windows identity of the user on the server.

On Mon, Nov 14, 2011 at 6:12 PM, Khash Sajadi <khash....@gmail.com> wrote:

That's right. It's all code based. Anything specific should be done in the client?

--
You received this message because you are subscribed to the Google Groups "Castle Project Development List" group.

To view this discussion on the web visit https://groups.google.com/d/msg/castle-project-devel/-/6bf7pwjbzVsJ.

[Valeriu Caraulean]

I have a project on GitHub with few examples on how to use WCF without config files.

I've added two projects to it - WebHost.Castle and a simple client project. Check it at:

 http://github.com/vcaraulean/WcfWithoutConfigFile/tree/master/WcfWithoutConfigFile.WebHost.Castle

 http://github.com/vcaraulean/WcfWithoutConfigFile/tree/master/WcfWithoutConfigFile.WebHost.Castle-Client

And the service code is making use of Service's SecurityContext...

Be sure that:

 - WcfWithoutConfigFile.WebHost.Castle is hosted in IIS Express

 - Windows Authentication is enabled for that project

Hope this helps...

On Mon, Nov 14, 2011 at 6:12 PM, Khash Sajadi <khash....@gmail.com> wrote:

That's right. It's all code based. Anything specific should be done in the client?

--
You received this message because you are subscribed to the Google Groups "Castle Project Development List" group.

To view this discussion on the web visit https://groups.google.com/d/msg/castle-project-devel/-/6bf7pwjbzVsJ.

[Khash Sajadi]

Awesome! It worked. I did this to get the client to be config-free as well:

            container

                .AddFacility<WcfFacility>()

                .Register(Types.FromAssemblyContaining<IMyService>()

                              .Where(t => t.Name.EndsWith("Service"))

                              .Configure(c => c.AsWcfClient(

                                  WcfEndpoint

                                      .BoundTo(new BasicHttpBinding() { 

                                          Security = 

                                          {

                                              Mode = BasicHttpSecurityMode.TransportCredentialOnly, 

                                              Transport = { ClientCredentialType = HttpClientCredentialType.Windows }

                                          } 

                                      })

                                      .At(ServiceNameHelper.GetServiceEndpoint(c.Implementation)))));

[Krzysztof Koźmic]

Would you guys care to add that to the documentation wiki for the next guy?

K

> --
> You received this message because you are subscribed to the Google
> Groups "Castle Project Development List" group.
> To view this discussion on the web visit

> https://groups.google.com/d/msg/castle-project-devel/-/_wNyVkPH9-gJ.

[Benny Hung]

The suggested workaround does work.  But is there a way to make this work with doing the configuration in config files?  Is this actually a bug in the wcf integration facility?

On a somewhat related note, what is the advantage of making things config-less?