[Openid-specs-ab] WebIntents-based OpenID Connect Discovery as a solution for NASCAR problem

[matake, nov]

Privacy issue because of using webintents.org's JS shim?
Then yes. They are not even providing the JS file via HTTPS :p

I didn't know account chooser WG is also looking into WebIntents.
I'll involve with them.

thanks

2012/4/10 John Bradley <ve7jtb at ve7jtb.com>

> Nov,
>
> There are some privacy issues around web intents<http://www.webintents.org/> and
> it's predecessor Xauth.
>
> The account chooser WG <http://sites.google.com/site/oidfacwg/> is
> currently looking at how to deal with that.   It is possible that they
> might support the web intents invocation if it makes it into browsers other
> than chrome at some point.
>
> At the moment to support a broad range of browsers they are using html5
> post message, much like the web intents JS shim.
>

> You should get involved with that WG.
>
> John B.
>
> On 2012-04-09, at 12:06 AM, matake, nov wrote:
>
> Hi all,
>
> WebIntents is one of the interesting features of HTML5, which enables
> browser-based inter-service delegation.
>
> Since it seems very useful as a solution of NASCAR problem, I've made a
> WebIntents-based OpenID Connect discovery demo using my OP & RP.
> You can try it following the step described in this post.
>
> http://t.oauth.jp/post/20756025471/when-you-access-to-an-openid-relying-party-rp
>
> I hope you guys are interested in it.
>
> Thanks
>
> ps.
> Now I'm thinking about how to standardize those 2 point.
> * WebIntents action for OpenID Connect discovery (need to discuss with W3C
> guys?)
> * OpenID Connect discovery endpoint for WebIntents (probably in OIDF)
>
> --
> nov
> _______________________________________________
> Openid-specs-ab mailing list
> Openid-specs-ab at lists.openid.net
> http://lists.openid.net/mailman/listinfo/openid-specs-ab
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs-ab/attachments/20120410/62855ab7/attachment.html>