-
Notifications
You must be signed in to change notification settings - Fork 0
problem using openid behind proxy #2
Comments
Ok, independently from realm setup from config, it seems it was related to a proxy configuration in Apache (missing ProxyPreserveHost On). Seems to "work" now. though, on page return it fails: after openid provider url is back to: http://mobyletest.genouest.org/login/openid/callback?janrain_nonce=2012-12-11T12%3A20%3A30ZDB7OMm and it ends with an 500 internal error |
The return url looks fine. You should have more details for the internal error on the console logs |
Here are the logs
|
looks like it's working now. BTW you should deactivate the pyramid debug toolbar, or set it to only recognize pre-defined IP. |
it will be deactivated, it was for testing. I still have the error. However, while testing with toolbar I see an error in the json.dump of views.py: TypeError: datetime.date(1974, 7, 29) is not JSON serializable the dump of the result from openid contains my birthdate, and it fails to serialize it. |
i was able to login on your portal, it worked but not anymore... |
works again just now |
When behind a web proxy, there is an issue with openid.
After authentication on remote provider, user is redirected back to the site on a wrong address, the one given in [server:main] for host and port.
It does not seem to take into account the value defined in init.py:
config.add_openid_login(realm='....
The text was updated successfully, but these errors were encountered: