------art_46928_30748276.1162141760166
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

On 10/29/06, khaines / enigo.com <khaines / enigo.com> wrote:
>
>
> I have a requirement for something like this right now.
>
> A web site with private content links to an external provider.  The users
> log into the private content with a standard userid/password
> authentication.
>
> The external provider trusts my authentication, so they want liks to them
> to encode the userid using a symetric algorithm with a specific key.  The
> users just see a url like:
>
> http://foo.com/place?1b12d9542f%2f33b1a4
>
> and feel all warm and fuzzy.  The external provider can recover the userid
> from that, though, and can thus give the user their specific content.



I probably shouldn't get into this because it's offtopic, but why not just
use a plain-vanilla federated identity solution with the external provider?

------art_46928_30748276.1162141760166--