<div>Hi all,</div><div><br></div>I absolutely <b>do not</b> want the OpenID Working Group to consider this at all (not that I think they will).<div><br></div><div>As a developer, I understand it the desire. being about to have the device consumer login to their Google/Yahoo/etc. account and use that to access other services sounds great. </div>
<div><br></div><div>But OpenID isn't about us, it's about a user-centric identity. </div>
<div><br></div><div>Proxy prompting for a username/password that we'd use to authenticate on their behalf for OpenID is just ludicrous. It's just the wrong thing to do. Some of the OpenID Identity Providers may not use passwords at all. They might use multi-factor authentication methods. As a relying party, I don't care what they use. We have some responsibilities as developers to uphold the values of the protocols we use. Proxy passwords in an app labeled "OpenID enabled" subverts those values.</div>
<div><br></div><div>Write the two sides to this. The web application that does OAuth that lets the user control what information to share - and have your BluRay app talk to your own web services. You'd end up getting a lot more benefits to user tracking, settings storage, profiling, feature updates, and a thousand other benefits offloading part of that app to the web anyway.</div>
<div><br></div><div>Jason</div><div><br></div><div><br><br><div class="gmail_quote">On Thu, Feb 11, 2010 at 1:04 PM, valentino miazzo <span dir="ltr"><<a href="mailto:valentino.miazzo@blu-labs.com" target="_blank">valentino.miazzo@blu-labs.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Hitoshi,<br>
<br>
I agree.<br>
More in general, this mechanism can be used to avoid to hard-code in the<br>
spec of the extension some constants.<br>
<br>
There are millions of connected BD players and HDTVs not able to parse HTML.<br>
The owners of these devices would find in the proposed extension another<br>
good reason to obtain an OpenID.<br>
<br>
Thanks,<br>
Valentino<br>
<br>
Hitoshi Uchida said the following on 11/02/2010 18.42:<br>
<div><div></div><div>> Hi Valentino,<br>
><br>
> I'm also would like OpenID/OAuth WG to consider the embedded devices<br>
> usecase which don't have a web browser.<br>
><br>
> I understand your consideration that definition of POST URLs to be<br>
> used for submit and trust operation is helpful for those embedded<br>
> devices.<br>
> However, I think it wouldn't be good solution to define the path of<br>
> URL like '/signin_submit' or '/trust_submit' as spec.<br>
><br>
> So my idea is that a below tag should be contained in the HEAD section<br>
> of the HTML loggin page sent by OP like OpenID HTML discovery.<br>
> <link rel="openid2.provider.signin openid.server.signin"<br>
> href="<a href="https://www.myopenid.com/signin_submit" target="_blank">https://www.myopenid.com/signin_submit</a>"/><br>
><br>
> Then, for instance, 'signin_id' and 'signin_password' parameters<br>
> representing user's account information would be sent against the URL.<br>
><br>
> And a below tag would be contained in the trust/deny HTML page sent<br>
> after the user's authentication.<br>
> <link rel="openid2.provider.trust openid.server.trust"<br>
> href="<a href="https://www.myopenid.com/trust_submit" target="_blank">https://www.myopenid.com/trust_submit</a>"/><br>
><br>
> Those simple tag can be parsed easily by embedded devices.<br>
> And also, such an additional link tag of HEAD section can keep interoperability.<br>
><br>
> What do you think ?<br>
><br>
> Best Regards,<br>
> Hitoshi Uchida<br>
><br>
><br>
><br>
> 2010/2/11 valentino miazzo <<a href="mailto:valentino.miazzo@blu-labs.com" target="_blank">valentino.miazzo@blu-labs.com</a>>:<br>
><br>
>> Chris, did you have a chance to read my answer?<br>
>> Does anyone has something to add?<br>
>><br>
>> Thanks<br>
>> Valentino<br>
>><br>
>> PS: Added Allen Tom and Hitoshi Uchida. They were discussing something<br>
>> similar in openid-user-experience ML.<br>
>> <a href="http://lists.openid.net/pipermail/openid-user-experience/2010-February/001119.html" target="_blank">http://lists.openid.net/pipermail/openid-user-experience/2010-February/001119.html</a><br>
>><br>
>> valentino miazzo said the following on 05/02/2010 10.34:<br>
>><br>
>> Hi Chris,<br>
>> with the name proposal I wanted to be funny but maybe I seemed not humble.<br>
>> Sorry for this.<br>
>><br>
>> I will try to be more clear about my proposal.<br>
>> Basically I see a low hanging fruit but, being a newbie with OpenId, maybe I<br>
>> overlook something.<br>
>><br>
>> As explained to Yang Zhao in another post I assume the user has a valid<br>
>> OpenId.<br>
>> I just want to be able to use such OpenId from limited devices.<br>
>> It's OK that the user used an HTML browser to create his account.<br>
>><br>
>> In my understanding of the OpenId user experience, the user interacts with<br>
>> OP HTML pages in at least 2 scenarios (as told, I intentionally exclude<br>
>> OpenId account creation):<br>
>> 1) the OpenId session is closed/expired and the user needs to login in his<br>
>> OpenId account with a one factor authentication.<br>
>> 2) a RP not in the trust list requested user authentication and the user is<br>
>> asked to trust it or deny. Plus the user can choose to add/remove the RP<br>
>> to/from the trust list.<br>
>><br>
>> For sure, an OP can add more features (2 factors authentications, Oauth,<br>
>> etc...) but this seems the minimal possible interaction with the OP HTML<br>
>> pages.<br>
>> The involved OP HTML pages eventually send a POST request to an URL that<br>
>> actually perform the login and trust management.<br>
>> My proposal is add an extension to the specifications that dictates how<br>
>> these 2 POST requests must be made.<br>
>> As concrete example, if MyOpenId decides to adopt this extension then it<br>
>> will change the code handling these 2 URLs<br>
>> <a href="https://www.myopenid.com/signin_submit" target="_blank">https://www.myopenid.com/signin_submit</a> ,<br>
>> <a href="https://www.myopenid.com/trust_submit" target="_blank">https://www.myopenid.com/trust_submit</a> to cope with the extension<br>
>> specifications.<br>
>><br>
>> Why do that? Because, in this way, user-agents not supporting HTML could<br>
>> just ignore the HTML pages and invoke the POST URLs directly.<br>
>> For users using an HTML browser nothing changes. POST syntax changes are<br>
>> completely invisible to the user.<br>
>> Maybe, OP supplying a richer user experience compared to what I described at<br>
>> point 1 and 2 can offer simplified HTML pages and serve them to limited<br>
>> devices.<br>
>><br>
>> Point 5 of the protocol overview of OpenId 2.0 specs<br>
>> (<a href="http://openid.net/specs/openid-authentication-2_0.html#anchor2" target="_blank">http://openid.net/specs/openid-authentication-2_0.html#anchor2</a>) says:<br>
>> <<5. The OP establishes whether the end user is authorized to perform OpenID<br>
>> Authentication and wishes to do so. The manner in which the end user<br>
>> authenticates to their OP and any policies surrounding such authentication<br>
>> is out of scope for this document. >><br>
>> So, the proposed extension doesn't overlaps in any way with the OpenId specs<br>
>> because this part was intentionally not part of the OpenId standard.<br>
>><br>
>> I tried, but I'm not able to found how this extension could change the<br>
>> existing security model of OpenId.<br>
>><br>
>> I'm very interested in knowing your (and others) opinion.<br>
>><br>
>> Thank you,<br>
>> Valentino<br>
>><br>
>><br>
>><br>
>> Chris Messina said the following on 04/02/2010 18.20:<br>
>><br>
>> It's unclear what kind of alternative you're proposing, Valentino.<br>
>> At some point, the user must interact with his/her IDP in order to validate<br>
>> the request — without a web browser involved, you'll have to figure out some<br>
>> way to interact with each IDP individually, which would likely require you<br>
>> to pre-register your client device with the IDP so that they can gauge<br>
>> whether to trust the request or not. Even still, that defeats the security<br>
>> model of OpenID.<br>
>> We've been down this path several times in the past several years and the<br>
>> result was OAuth.<br>
>> While it may seem inelegant to have the user interact with a secondary<br>
>> browser-enabled device to authorize access to their account, we've yet to<br>
>> come up with a scalable, universal solution that is also secure.<br>
>> You may have name for your solution, but how would it work technically? What<br>
>> would the user experience be like? And how would it keep the user safe?<br>
>> Curious to hear your proposal.<br>
>> Chris<br>
>><br>
>> On Thu, Feb 4, 2010 at 9:18 AM, Andrew Arnott <<a href="mailto:andrewarnott@gmail.com" target="_blank">andrewarnott@gmail.com</a>><br>
>> wrote:<br>
>><br>
>>> Well, OAuth WRAP partially solves the problem because the protocol<br>
>>> actually has a profile that doesn't require a web browser. It requires that<br>
>>> the client app collect the username+password of the user, which it then<br>
>>> forwards to the service provider in exchange for the WRAP token.<br>
>>> The downsides of this approach is that it depends on the user having a<br>
>>> username+password to begin with (which if it's a pure OpenID account, or<br>
>>> Infocard, etc. there won't be one) and it requires the user to disclose the<br>
>>> password to a third party.<br>
>>> --<br>
>>> Andrew Arnott<br>
>>> "I [may] not agree with what you have to say, but I'll defend to the death<br>
>>> your right to say it." - S. G. Tallentyre<br>
>>><br>
>>><br>
>>> On Thu, Feb 4, 2010 at 6:10 AM, valentino miazzo<br>
>>> <<a href="mailto:valentino.miazzo@blu-labs.com" target="_blank">valentino.miazzo@blu-labs.com</a>> wrote:<br>
>>><br>
>>>> Andrew Arnott said the following on 04/02/2010 14.48:<br>
>>>><br>
>>>>> You're correct, Valentino. In OAuth, a device without a web browser on<br>
>>>>> it must indicate to the user to find a web browser [on another device]<br>
>>>>> to authorize the token.<br>
>>>>><br>
>>>>><br>
>>>> Ask to a user in the sofa (watching a bluray movie) to find a web<br>
>>>> browser to login and then go back is not an option. Nobody will do it.<br>
>>>> So, it seems Oauth has the same limits of OpenId from this point of view.<br>
>>>><br>
>>>> Returning to solution C ... in the opinion of you, experts and founders<br>
>>>> of OpenId and Oauth, there is any chance that a some point OpenId<br>
>>>> Providers will converge on a common "submit API" ?<br>
>>>> I have already the name: Embedded OpenId<br>
>>>> :)<br>
>>>><br>
>>>> Thanks.<br>
>>>> Valentino<br>
>>>><br>
>>>><br>
>>>><br>
>>><br>
>><br>
>><br>
>> --<br>
>> Chris Messina<br>
>> Open Web Advocate, Google<br>
>><br>
>> Personal: <a href="http://factoryjoe.com" target="_blank">http://factoryjoe.com</a><br>
>> Follow me on Twitter: <a href="http://twitter.com/chrismessina" target="_blank">http://twitter.com/chrismessina</a><br>
>><br>
>> This email is: [ ] shareable [X] ask first [ ] private<br>
>><br>
>><br>
><br>
><br>
><br>
</div></div><div><div></div><div>_______________________________________________<br>
Code mailing list<br>
<a href="mailto:Code@lists.openid.net" target="_blank">Code@lists.openid.net</a><br>
<a href="http://lists.openid.net/mailman/listinfo/openid-code" target="_blank">http://lists.openid.net/mailman/listinfo/openid-code</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~<br>Jason Young -- Engineering Manager, eXtension<br><a href="http://about.extension.org/wiki/Jason_Young" target="_blank">http://about.extension.org/wiki/Jason_Young</a><br>
______________________________________<br>
</div>