Martin v. Löwis wrote:
Even not having provider changes supported would still allow me to use
my openid with PyPI which would be great. The only problem with changing
provider that I can see is when the provider a user changes to would
then be a duplicate - in which case I think just refusing to allow the
login would be fine (rather than changing the provider for that account).
In that case, it would be much easier to record your true openid (i.e.
the one that your provider is able to validate). You can then enter the
alias that you are used to, and PyPI would map that right away to the
verifiable ID, and log you in with that.
Would it be possible to detect a change of provider and then offer the
option to migrate the account to the new provider (so long as it does
not conflict with another account)?
For this to work, you would have to upgrade your web page to OpenID 2,
as this is the only protocol that PyPI supports.
This I can do.
Thanks
Michael
Regards,
Martin
--
http://www.ironpythoninaction.com/
http://www.voidspace.org.uk/blog
_______________________________________________
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
