Dear All, Having got the basic geonode install working (hurrah), I am trying to use a remote geoserver instance. I have changed the GEOSERVER_BASE_URL in /var/www/geonode/wsgi/geonode/src/GeoNodePy/geonode/local_settings.py to match the remote geoserver instance, but when I run # /var/www/geonode/wsgi/geonode/bin/django-admin.py syncdb --settings=geonode.settings I get a tomcat 401 error, saying I have bad credentials, which I would expect because I haven't added the username and password anywhere. Where would I add this, and as a related question, can I only connect to remote geoserver instances which use the same modified war file that comes with the geonode download? Thanks Jo -- ----------------------------------------------------- Joanne Cook Senior IT Support and Development Oxford Archaeology (North) 01524 880212 http://thehumanjourney.net ------ Files attached to this email may be in ISO 26300 format (OASIS Open Document Format). If you have difficulty opening them, please visit http://iso26300.info for more information.
Connecting to "stock" geoserver is not very well supported right now, but it should be doable. GeoNode uses GEOSERVER_CREDENTIALS setting to connect to geoserver, this needs to be a Python tuple with the username and password for an administrative user. When using the modified GeoServer WAR we provide, GeoNode is providing the authentication database for GeoServer, so we can ensure that these credentials are valid... otherwise, it's up to you to keep them synchronized (and the permissions settings in the GeoNode UI have no effect). There are some other additions to GeoServer that help GeoNode provide its features - without them downloading data from the search page won't work, among other things. Is it possible for you to try migrating your GeoServer configuration over to a GeoNode-customized installation of GeoServer? It should be a simple matter of setting the GEOSERVER_DATA_DIR environment variable properly. I'd recommend making a backup first though, just in case :) -- David Winslow OpenGeo - http://opengeo.org/ On Tue, Dec 14, 2010 at 12:29 PM, Joanne Cook <j.cook@oxfordarch.co.uk>wrote: > Dear All, > > Having got the basic geonode install working (hurrah), I am trying to use a > remote geoserver instance. I have changed the GEOSERVER_BASE_URL in > /var/www/geonode/wsgi/geonode/src/GeoNodePy/geonode/local_settings.py to > match the remote geoserver instance, but when I run > # /var/www/geonode/wsgi/geonode/bin/django-admin.py syncdb > --settings=geonode.settings > I get a tomcat 401 error, saying I have bad credentials, which I would > expect because I haven't added the username and password anywhere. > > Where would I add this, and as a related question, can I only connect to > remote geoserver instances which use the same modified war file that comes > with the geonode download? > > Thanks > > Jo > -- > ----------------------------------------------------- > Joanne Cook > Senior IT Support and Development > Oxford Archaeology (North) > 01524 880212 > http://thehumanjourney.net > > > ------ > Files attached to this email may be in ISO 26300 format (OASIS Open > Document Format). If you have difficulty opening them, please visit > http://iso26300.info for more information. > >
Hi David, Thanks- that is what I suspected. My remote data is already in a separate data_dir, so hopefully changing the geoserver war file ought not be too painful. Cheers Jo ----- Original Message ----- From: "David Winslow" <dwinslow@opengeo.org> To: geonode@librelist.com Sent: Tuesday, 14 December, 2010 5:39:33 PM Subject: Re: [geonode] Using a remote geoserver instance with geonode Connecting to "stock" geoserver is not very well supported right now, but it should be doable. GeoNode uses GEOSERVER_CREDENTIALS setting to connect to geoserver, this needs to be a Python tuple with the username and password for an administrative user. When using the modified GeoServer WAR we provide, GeoNode is providing the authentication database for GeoServer, so we can ensure that these credentials are valid... otherwise, it's up to you to keep them synchronized (and the permissions settings in the GeoNode UI have no effect). There are some other additions to GeoServer that help GeoNode provide its features - without them downloading data from the search page won't work, among other things. Is it possible for you to try migrating your GeoServer configuration over to a GeoNode-customized installation of GeoServer? It should be a simple matter of setting the GEOSERVER_DATA_DIR environment variable properly. I'd recommend making a backup first though, just in case :) -- David Winslow OpenGeo - http://opengeo.org/ On Tue, Dec 14, 2010 at 12:29 PM, Joanne Cook < j.cook@oxfordarch.co.uk > wrote: Dear All, Having got the basic geonode install working (hurrah), I am trying to use a remote geoserver instance. I have changed the GEOSERVER_BASE_URL in /var/www/geonode/wsgi/geonode/src/GeoNodePy/geonode/local_settings.py to match the remote geoserver instance, but when I run # /var/www/geonode/wsgi/geonode/bin/django-admin.py syncdb --settings=geonode.settings I get a tomcat 401 error, saying I have bad credentials, which I would expect because I haven't added the username and password anywhere. Where would I add this, and as a related question, can I only connect to remote geoserver instances which use the same modified war file that comes with the geonode download? Thanks Jo -- ----------------------------------------------------- Joanne Cook Senior IT Support and Development Oxford Archaeology (North) 01524 880212 http://thehumanjourney.net ------ Files attached to this email may be in ISO 26300 format (OASIS Open Document Format). If you have difficulty opening them, please visit http://iso26300.info for more information. -- ----------------------------------------------------- Joanne Cook Senior IT Support and Development Oxford Archaeology (North) 01524 880212 http://thehumanjourney.net ------ Files attached to this email may be in ISO 26300 format (OASIS Open Document Format). If you have difficulty opening them, please visit http://iso26300.info for more information.