What does this Openid error mean: error trying to use stored discovery information

Question

I am trying to configure an application using django-openid and openid. I get the following errors and I can not understand what causes them.

[Fri Jan 29 13:29:20 2010] [error] Generated checkid_setup request to https://www.google.com/accounts/o8/ud with assocication XXXXXXXXXXXXXX [Fri Jan 29 13:29:26 2010] [error] Error attempting to use stored discovery information: <openid.consumer.consumer.TypeURIMismatch: Required type http://specs.openid.net/auth/2.0/signon not found in ['http://specs.openid.net/auth/2.0/server', 'http://openid.net/srv/ax/1.0', 'http://specs.openid.net/extensions/ui/1.0/mode/popup', 'http://specs.openid.net/extensions/ui/1.0/icon', 'http://specs.openid.net/extensions/pape/1.0'] for endpoint <openid.consumer.discover.OpenIDServiceEndpoint server_url='https://www.google.com/accounts/o8/ud' claimed_id=None local_id=None canonicalID=None used_yadis=True >> [Fri Jan 29 13:29:26 2010] [error] Attempting discovery to verify endpoint [Fri Jan 29 13:29:26 2010] [error] Performing discovery on https://www.google.com/accounts/o8/id?id=PrHw_N5_3j1HM [Fri Jan 29 13:29:26 2010] [error] Received id_res response from https://www.google.com/accounts/o8/ud using association XXXXXXXXXXXXX 

It seems that Python cannot use the information that is retrieved from Google. Is this error due to data coming from Google, or is it a problem with openid?

Answer 1

Hm. This is not really a fatal error; I get the same when using the python-openid user example against the google OP id (/ accounts / o8 / id, which generates adjacent directed identifiers), but it logs in successfully.

This probably causes some log spam if you have a google login button and the library might be referred to so as not to try to use the stored discovery information when it was for the OP identifier, but if you don’t using you can log in, something else is your problem.

Answer 2

This happens when the specified URL is the server URL and not the Authenticated Identifier. This is a genuine error for the path that generates it, because the URL cannot be used as an identifier, but it gets inside and is used to request a true identifier from the server, so it is safe to ignore log messages. However, an error report was sent to the python-openid project on GitHub with a suggested fix.