Re: CryptoAPI cryptographic service provider (CSP) for this implementation could not be acquired

From: Willy Denoyette [MVP] (willy.denoyette@pandora.be)
Date: 07/24/02 

From: "Willy Denoyette [MVP]" <willy.denoyette@pandora.be>
Date: Wed, 24 Jul 2002 20:18:46 +0200

"Allen Owen" <alleno@intenda.co.za> wrote in message news:uv6uc7uMCHA.2436@tkmsftngp11...
> Hi,

> This is one possible solution. Another is to turn impersonation on and thus
> user the impersonated user's keystore.
>

This is not true, as the impersonating users profile is not loaded , you can't access the user's keystore.

Willy.

Relevant Pages

  • Re: CryptoAPI cryptographic service provider (CSP) for this implementation could not be acquired
    ... I thought you could load the users profile by specifically including his ... user name and password in the impersonation tag? ... The documentation seems to ... >> user the impersonated user's keystore. ...
    (microsoft.public.dotnet.framework.aspnet.security)
  • Re: How can roles be determined for a resource?
    ... I half-agree that impersonation is needed... ... not because URL Authorization requires it. ... this problem you don't have to turn impersonation on site-wide ... I agree that impersonation site-wide can be a nasty thing ...
    (microsoft.public.dotnet.framework.aspnet.security)
  • Re: How can roles be determined for a resource?
    ... Impersonation should only be required here if you have applied a Windows ... > this problem you don't have to turn impersonation on site-wide ... I agree that impersonation site-wide can be a nasty thing ...
    (microsoft.public.dotnet.framework.aspnet.security)