<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
        {font-family:Calibri;
        panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
        {font-family:Tahoma;
        panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0in;
        margin-bottom:.0001pt;
        font-size:11.0pt;
        font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
        {mso-style-priority:99;
        color:blue;
        text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
        {mso-style-priority:99;
        color:purple;
        text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
        {mso-style-priority:99;
        mso-style-link:"Balloon Text Char";
        margin:0in;
        margin-bottom:.0001pt;
        font-size:8.0pt;
        font-family:"Tahoma","sans-serif";}
span.BalloonTextChar
        {mso-style-name:"Balloon Text Char";
        mso-style-priority:99;
        mso-style-link:"Balloon Text";
        font-family:"Tahoma","sans-serif";}
span.EmailStyle19
        {mso-style-type:personal;
        font-family:"Calibri","sans-serif";
        color:windowtext;}
span.EmailStyle20
        {mso-style-type:personal-reply;
        font-family:"Calibri","sans-serif";
        color:#1F497D;}
.MsoChpDefault
        {mso-style-type:export-only;
        font-size:10.0pt;}
@page Section1
        {size:8.5in 11.0in;
        margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
        {page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=EN-US link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal>Hello,<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>I am new to this group and OpenID in general so apologies if
I repeat questions already asked here before. I did try to read a few months of
backlog to catchup.<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>I’ve spent the past 10 days implementing OpenID support for
session authentication. I am currently working on an OpenId 2.0 RP
implementation in C++ for a web service I am developing. The idea is to use
OpenId to authenticate users’ access to the API which is a framework enabling
developers to build their own micro-blogging sites. Due to the nature of the
platform, I am forced to implement the RP logic from scratch. The C++ libraries
found are all 1.1, and I am not sure what is the state of the 2.0 libraries.<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>I have been studying the spec and came up with a long list
of issues and open questions mostly through implementation. I will post each
question/issue separately to make it easier to track the threads and better
archive the conversation. If this is annoying please let me know.<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>This question is based on draft 11 of OpenID Authentication
2.0.<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>Section 2 describe the User-Supplied Identifier, and section
3 bullet 2 provided the workflow, allowing users to provide a User Identity or
an OP Endpoint ID. Section 7.3.1 provides a little more information but not much.
The document is not very clear about the difference and how to decide what ID
the user supplied. It is critical as the end of section 7.3.1 requires special
value of the id fields to be used with an OP Endpoint.<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>If the ID discovery leads to an XRDS document, I am guessing
that if that document contains an OP Identifier element, it might mean that
this is a server Id, but what if it also contains a claimed Id element? Is that
not allowed? And in that case, is the Canonical Id ignored? But this theory only
works for XRDS discovery. What about HTML discovery? Also, is there a
difference in the handling of an XRDS discovery depending on how it was
attained (XRI or Yadis)?<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>Also, should I be using / referencing a newer version of the
2.0 draft?<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>Thanks,<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>Eran Hammer-Lahav (=eran)<o:p></o:p></p>
<p class=MsoNormal>Hueniverse, LLC<o:p></o:p></p>
<p class=MsoNormal><a href="http://hueniverse.com">http://hueniverse.com</a><o:p></o:p></p>
</div>
</body>
</html>