Comment 4 for bug 536625

if i understand correctly, then login.launchpad.net will be the "openid provider" and launchpad.net will be the "relying party".

if that is the case then there is no need to list the authenticated sites on the launchpad profile. because the launchpad profile is for the launchpad website, which has nothing to do with openid other than the fact that it is an openid consumer. it just happens to be the login.launchpad.net openid which i just used to login, but it could have been any other openid.

the list of authenticated sites is then correctly located at login.launchpad.net.

but it would still be irritating (for me, but i am sure for many others) because launchpad.net and login.launchpad.net is only separated by a subdomain. also it feels a bit counterintuitive for me to use a service from a subdomain to login to a website located "above" the subdomain. then again, openid is openid, it doesn't matter from which (sub)domain your openid comes from.

at least it should be communicated clearly to the user. right now, in my profile page, i see a "(What's this?)" link after my openid url. that would be a good place to tell the user that launchpad.net is only the consumer, while login.launchpad.net is the openid provider. so if the user wants more information about his launchpad openid he should go to login.launchpad.net.