-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SESSION_EXPIRED_CONTROL_ENABLE=True breaks SPC GeoNode #4322
Comments
I´m experiencing something similar in dev setup from master branch:
It´s working again with: Do I miss something regarding oauth2 settings on a fresh paver start? |
Uhm, very bad... are you using the sqllite db? |
Yep, standard:
|
Taking a look |
@afabiani sorry to report this, but getting locked database with postgis in production as well. Cannot see anything wrong with oauth2. Logs mention the h2 store?!
|
@t-book I'm going to push a fix, it looks that django messages is not thread safe or at least it is not safely closing the db connections. About the second issue, it is not related to oauth2. It looks to me a permission issue with the geofence db file. About this last point, I kindly suggest to setup GeoFence rules to work against a postgres db in production and not with the default h2 one. The same is valid for the GeoServer disk-quota (if any has been configured). |
which is described here: https://github.com/geoserver/geofence/wiki/GeoFence-configuration
no idea where to do this. |
[Fixes #4322] SESSION_EXPIRED_CONTROL_ENABLE=True breaks GeoNode
|
Here's what happens when setting
SESSION_EXPIRED_CONTROL_ENABLE=True
(default value in GeoNode, but set toFalse
in SPCGeonode):@afabiani said about that (in Gitter):
The text was updated successfully, but these errors were encountered: