"Pablo Cibraro" wrote:

> Hi YC,
>
> 1. That is strange, if you reuse the same proxy instance, the
> RequestSecurityToken message should be sent once. Have you tried to reuse
> the SCT ?. This article in my blog describes how to do that,
> http://weblogs.asp.net/cibrax/archive/2006/02/21/438670.aspx
>
> 2. Yes, WSE keeps the certificates in a cache for performance reasons.
>
> Regards,
> Pablo Cibraro
> http://weblogs.asp.net/cibrax
>
> "YC" <YC@discussions.microsoft.com> wrote in message
> news:83F9A2DB-A18E-4306-9689-6C4A3B48ECC5@microsoft.com...
> > Hi,
> > I have 2 questions regarding WSE 3.0:
> > 1) Using sct with asp.net application as client - I implemented sct with
> > an
> > asp.net web application as a client. I can see in the trace files that the
> > element <wst:RequestSecurityToken> gets created each time I invoke the
> > specific web method with the sct. Even if I save the proxy in session it's
> > being created each method call.
> >
> > 2) Certificates private key caching - does the WSE cache the certificate
> > keys?
> > I had a problem in which I needed to add the Network Services for ntfs
> > permissions on a certificate private key. I had to restart iis in order
> > for
> > the WSE to except the changes I've made.
> >
> > Can anyone explain this behavior?
> >
> > Thanks
> >
> > Yoav
> >
>
>