+2  A: 

www.claimid.com is not an OpenID 2.0 Provider. It only supports OpenID 1.1. Therefore, typing www.claimid.com into an OpenID relying party will not work (OpenID 1.1 does not include identifier_select functionality, which is what you're trying to do). You have to type in the individual's OpenID. Try typing in claimid.com/aarnott and it will work just fine.

myopenid.com on the other hand is an OpenID 2.0 Provider, which is why you see that one working for you.

Andrew Arnott
A: 

Hi, Thank you for your feedback. I have tried your suggestion and unfortunately it doesn't work.

  1. Updated OpenIdRelyingParty constructor in DotNetOpenAuth.OpenId.RelyingParty.UserController to use null as IRelyingPartyApplicationStore
  2. Run the sample
  3. Pass claimid.com/aarnott to the OpenId input
  4. ProtocolException: No OpenID endpoint found.

The same sample works if I use the default parameterless constructor for OpenIdRelyingParty. I ran the sample on my local machine.

Any idea?

please edit your original question, do not post an answer containing another question
Marek
A: 

I think this whole ClaimID thing is broken anyway. I tried several times to register there, but a) there is no link to register anywhere and b) even trying to sign in with an existing OpenID won't work (after pressing "Continue" in myOpenID I just get forwarded to the log-in page of ClaimID again => endless loop)..

Also the last entry of the ClaimID blog (blog.claimid.com) is from Feb 09 and talks about a paid version etc., so I wouldn't hold my breath on ClaimID getting anywhere in the future