RE: WSE 3.0 usernameForCertificateSecurity doubt
- From: lukezhan@xxxxxxxxxxxxxxxxxxxx (Luke Zhang [MSFT])
- Date: Thu, 29 Jun 2006 05:40:39 GMT
{\rtf1\ansi\ansicpg936\deff0\deflang1033\deflangfe2052{\fonttbl{\f0\fnil\fprq2\fcharset0 MS Sans Serif;}}
\viewkind4\uc1\pard\lang2052\f0\fs20 Hello Jeffrey,
\par
\par I have to say this is impossible. The usernameForCertificateSecurity must use X.509 certificates stored in CurrentUser or LocalMachine.
\par
\par Regards,
\par
\par Luke Zhang
\par Microsoft Online Community Lead
\par
\par ==================================================
\par When responding to posts, please "Reply to Group" via your newsreader so that others may learn and benefit from your issue.
\par ==================================================
\par
\par (This posting is provided "AS IS", with no warranties, and confers no rights.)
\par
\par }
- References:
- WSE 3.0 usernameForCertificateSecurity doubt
- From: Jeffrey Sánchez
- WSE 3.0 usernameForCertificateSecurity doubt
- Prev by Date: Re: WSE 3.0, usernameOverTransportSecurity, custom Token Manager w/ securityTokenManager,
- Next by Date: Newbie: Problem with AuthenticateToken-Function - not called
- Previous by thread: WSE 3.0 usernameForCertificateSecurity doubt
- Next by thread: Newbie: Problem with AuthenticateToken-Function - not called
- Index(es):
Relevant Pages
|
|
