Thanks for your answers. The updatelayers worked fine. Now I understand the role of the geoserver_admin user. The question about using a "stock" geoserver was just about the possibility. We already have a geoserver instance with many layers and would be nice to use it without replacements. However we can migrate the data dir into the custom geoserver with no particular issues.
Now is clearer. Thanks again. Simone 2011/2/25 David Winslow <[email protected]> > On Fri, Feb 25, 2011 at 6:10 AM, Simone Dalmasso < > [email protected]> wrote: > >> Hi list, I'm trying to deploy geonode on a Debian 6 installation. >> I've set up the environment with the release 1.0 of geonode but using the >> latest Geonetwork release (adding geonode metadata schema). >> >> All seems to work pretty fine except for the fact that the layers created >> directly in geoserver or added by copying xml files from other geoserver >> data dirs, are accessible only if I am logged in as django admin or as >> geoserver_admin. If I log out they disapper from layer preview and >> Geonetwork no longer access them. >> I tried to add two data security rules like *.*,r and *.*,w but with no >> success. >> > > GeoNode *replaces* the normal GeoServer security system for better > integration with the Django user system. The default security setting for > layers is admin-only. In order to change the settings for a layer you have > to get it into the geonode database. Then you can visit the GeoNode's page > for the layer to change the security settings for it. > Getting it into geonode is pretty easy - there's a script that does it for > you: > > django-admin.py updatelayers --settings=geonode.settings > > >> The other question is: which is the difference between the geoserver_admin >> and the django admin? And how can I change the geoserver_admin password >> which is coded into the geoserver_token file? >> > > Don't try to use that account manually, any admin account in the Django app > is also an admin account in GeoServer. geoserver_token is used just for > "anonymous" operations (like the updatelayers script). > > And finally, how about using a "stock" existing geoserver with geonode? >> Just modifying parameters in the settings doesn't work while uploading new >> shapefile. >> > > I don't understand this question. What are you trying to do? What happened > instead? Why would a GeoServer install without our customizations do it > better? > > >> Thanks a lot in advance. >> -- >> Simone Dalmasso, Eng. >> ITHACA >> Information Technology for Humanitarian Assistance, Cooperation and Action >> www.ithacaweb.org >> Via Pier Carlo Boggio 61 - 10138 Torino >> Tel: +39.011.1975.1854 >> > > -- Simone Dalmasso, Ing. ITHACA Information Technology for Humanitarian Assistance, Cooperation and Action www.ithacaweb.org Via Pier Carlo Boggio 61 - 10138 Torino Tel: +39.011.1975.1854
