[OpenID] Calling OpenID 2.0 editors (was RE:Problems withOpenID and TAG httpRange-14)

[Eddy Nigg (StartCom Ltd.)]

Hi Noah,

Noah Slater:
> On Thu, Mar 06, 2008 at 09:58:08PM +0200, Eddy Nigg (StartCom Ltd.) wrote:
>> No, but neither does the "originally requested resource" must be the
>> claimed_id
>>     
>
> I'm sorry, can you rephrase this?
>   
Sure :-) See below...
> If I claim <http://bytesexual.org/> as my OpenID and this 303s to some place
> else it is pretty clear what my "claimed id" is, unless that phrase carries
> extra semantics which I am not aware off.
>
>   
>> http://john.example.com/ is the claimed_id, not a redirect. Of course
>> one might submit http://john.example.com/ as the claimed_id from the
>> beginning, but it's not required.
>>     
>
> Again, sorry, I am having trouble understanding your point.
>
> Would you mind rephrasing?
I think the example above does illustrate practically what happens. The 
ID http://bytesexual.org/ can be redirected to a completely different 
provider (lets say http://id.microsoft.com/ which confirms this as your 
ID, but also could return http://noah.bytesexual.org/ or anything else 
as your claimed_id (whatever your real ID is, or one of your real IDs).

Please note (and I also needed some time to understand this in the code 
and OpenID slang), that the claimed_id *is* your ID, it has nothing to 
do with what you claim is your ID (for example: I claim that 
"bytesexual.org" is my ID and this is what I'm going to submit into the 
RP text field. The claimed_id doesn't have to be "bytesexual.org", but 
whatever the OP returns to the RP is the claimed_id (it's not about what 
you claim....)

-- 
Regards 
 
Signer:  	Eddy Nigg, StartCom Ltd. <http://www.startcom.org>
Jabber:  	startcom at startcom.org <xmpp:startcom at startcom.org>
Blog:  	Join the Revolution! <http://blog.startcom.org>
Phone:  	+1.213.341.0390
 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-general/attachments/20080306/b404b1d9/attachment-0002.htm>