Re: Propagating caller identity across applications from a bare ASMX Service method to a WSE3 Service method

{\rtf1\ansi\ansicpg936\deff0\deflang1033\deflangfe2052{\fonttbl{\f0\fnil\fprq2\fcharset0 MS Sans Serif;}}
\viewkind4\uc1\pard\lang2052\f0\fs20 Thanks for your reply Howard,
\par
\par Yes, some of the articles I've ever refered in some previous threads. For the S4U/constrained delegation, you can consider using it in your own service-side(can won't affect the edge service on your partner's side). That means, you can let your partner call your service and pass windows identity in your first proxy service, you no longer need to pass the full identity/credentials. Just pass the user principal name and at your backend service, just generate a windowsIdentity through the user principal name(as described in the constrained delegation reference).
\par
\par Sincerely,
\par
\par Steven Cheng
\par
\par Microsoft MSDN Online Support Lead
\par
\par
\par
\par This posting is provided "AS IS" with no warranties, and confers no rights.
\par
\par }

Relevant Pages
Loading