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 <[email protected]>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. > > To post to this group, send email to [email protected] > . > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/castle-project-devel?hl=en. > -- You received this message because you are subscribed to the Google Groups "Castle Project Development List" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/castle-project-devel?hl=en.
