What do you want to accomplish by adding the geonode "kool aid"? Most of the functionality in GeoNode's GeoServer is either custom functionality that isn't designed for general use (the security system) or generally available (the print extension for geoserver.)
If it's just the ease of having a couple of extensions pre-installed, you can do that yourself in a few ways; one of the easiest is just to add the extensions to a GeoServer instance and zip it back up into a .war file. It definitely is possible to have multiple security backends working together in the security framework, but the previous behavior that allowed using geoserver's standard security implementation in geonode was a bug and a security hole. As you mention, it allowed bypassing the security restrictionsas configured by GeoNode users. -- David Winslow OpenGeo - http://opengeo.org/ On Thu, Jun 30, 2011 at 11:00 AM, Ariel Nunez <[email protected]>wrote: > Another thing that crossed my path yesterday is that after convincing > my friend to use the 'genode' compatible version of Geoserver > (geoserver-geonode-dev.war) I realized that he was going to have to > set up the python side of GeoNode too to be able to use the basic > GeoServer. > > As far as I know it is possible to use normal GeoServer authentication > along with GeoNode auth, right? Then would it make sense to allow > people to use a geoserver with the geonode kool aid in but without > having to switch GeoNode right away? > > This might not make much sense because of the permissions framework > for layers but wanted to get your thoughts (especially Gabriel's) > about wether it might be feasible. > > Ariel. >
