Re: W3C Web Payments, PaySwarn and OpenTransact

Hi David,
Sorry I should have included a link.

http://openid.net/connect/

The original OpenID was incredibly complex, which is why commercial
alternatives like twitter login and facebook connect gained ground using
oauth and oauth2 respectively.

The problem with using a token as a user identifier is that it then needs
to be permanent. OpenID Connect solves it by adding a separate id_token to
a OAuth2 authentication request, which can be used as a user identifier.

The clever thing is that it can be combined with any other OAuth 2
authorization request such as an OpenTransact authorization request. This
means you can authorize a payment as well as provide identity information
to a merchant in a simple step.

P

On Fri, Dec 16, 2011 at 5:22 PM, David Nicol <davidnicol@gmail.com> wrote:

> what's a good introductory link for "openid connect?"
>
> On Fri, Dec 16, 2011 at 2:18 PM, Pelle Braendgaard <
> pelle@stakeventures.com> wrote:
>>
>> OpenTransact builds on OAuth 2 and http. It can coexists well with OpenID
>> Connect (not to be confused with traditional OpenID).
>>
>
> --
> Application of Porter's value chain model to the executive function
> reveals that the executive process transforms the input of information into
> the output of decisions.
>



-- 
http://picomoney.com - Like money, just smaller
http://stakeventures.com - My blog about startups and agile banking