Hi Eric,
Your supposition is correct at certain extent. You can use the Windows
Principal available in the kerberos token to check permissions at method
level.
Another solution is to extend the Kerberos assertion provided by WSE to set
the CurrentThread.Principal property with the principal available in the
kerberos token. Once, you do that, you can use PrincipalPermission to set
permissions at method level.
Regards,
Pablo Cibraro.
>I am designing some services that I am thinking would be good to secure
>using Kerberos as we have an intranet setup. It is pretty clear how you
[quoted text clipped - 12 lines]
> Thanks,
> Eric
Howard Hoffman - 09 Jan 2007 22:41 GMT
We've written a custom PolicyAssertion / SoapFilter pair of subclasses that
grab the SecurityToken out of SoapEnvelope.Context.Credentials, create a
RoleProviderPrincipal if necessary, check IsInRole membership against roles
configured for the SoapEnvelope.Context.Addressing.Action and ultimately
populate the Thread.CurrentPrincipal.
The SoapEnvelope SecurityTokens will be populated by the WSE pipeline, so
you're not just limited to Kerberos.
We've found it to be very useful, as we have lot's of different services on
the same ASMX.
HTH,
Howard Hoffman
> Hi Eric,
>
[quoted text clipped - 25 lines]
>> Thanks,
>> Eric