Files changed (2)
* A Django ``User`` object. In this case, the OpenID claim was successfully authenticated, and the backend found a user in the database with this claim attached. The object as additional attributes:
* ``openid_claim``: The claim that was finally authenticated. Depending on the OpenID provider, this might or might not be the original method input. In a later call to ``linkOpenID``, use only this one.
+ * ``openid_ax``: A dictionary of received AX values. The ``django.contrib.auth.AX`` dictionary contains a list of standardized key names. Check the openid2rp documentation for more information.
* A Django ``AnonymousUser`` object. In this case, the claim could not be related to any user in the database, but the OpenID authentication was ok. The object has the same additional attributes as above. In this situation, you should normally proceed with some new user registration functionality. You can use the AX / SREG data to pre-fill some registration form.
# we need to accept some difference between provider time and our time, for nonce and session checking