Closed ScottEvil closed 11 years ago
Commit fbb19d9e7ed69ec2b779741d52ad994a16ba0e03 resolves this on the Geonode side. To enable the functionality we can just change LOCKDOWN_GEONODE = True
in settings.py
@garnertb ... is this something we could potentially migrate upstream to geonode proper? We have heard this feature requested before.
On Mon, Aug 19, 2013 at 8:28 AM, Tyler Garner notifications@github.comwrote:
Commit fbb19d9https://github.com/ROGUE-JCTD/rogue_geonode/commit/fbb19d9e7ed69ec2b779741d52ad994a16ba0e03resolves this on the Geonode side. To enable the functionality we can just change LOCKDOWN_GEONODE = True in settings.py
— Reply to this email directly or view it on GitHubhttps://github.com/ROGUE-JCTD/rogue_geonode/issues/14#issuecomment-22880284 .
@jj0hns0n, I think upstream is the right place for this. Want me to submit a PR?
Yep, this may require a GNIP, but go ahead and file an issue and then a PR and we will discuss.
On Mon, Aug 19, 2013 at 8:45 AM, Tyler Garner notifications@github.comwrote:
@jj0hns0n https://github.com/jj0hns0n, I think upstream is the right place for this. Want me to submit a PR?
— Reply to this email directly or view it on GitHubhttps://github.com/ROGUE-JCTD/rogue_geonode/issues/14#issuecomment-22881611 .
We're going to have to have a more "locked down" instance of ROGUE where the user is immediately challenged with a login and cannot see anything (GeoNode or Salamati) until they authenticate. That authentication needs to carry through GeoNode and GeoServer