[GeoNode-devel] Geoserver Layers from 2.4 to 2.6 - permissions
skeenamaps at gmail.com
Wed Dec 20 20:16:45 PST 2017
Could you please provide a bit more detail on what I need to tweak in
Geoserver security? Also, how do regenerate the layer permissions--I have
tried both manage.py updatelayers and manage.py updatemaplayerip, are there
any other commands I can use?
On Tue, Dec 19, 2017 at 7:37 AM, Alessio Fabiani <
alessio.fabiani at geo-solutions.it> wrote:
> new versions of GeoServer are able to automatically upgrade the data dir
> (make a backup of the old one anyway), however depending on the version of
> GeoServer you want to use and version of GeoNode, you will need to tweak a
> bit the GeoServer security and regenerate the layer permissions.
> Alessio Fabiani
> GeoServer Professional Services from the experts! Visit
> http://goo.gl/it488V for more information.
> Ing. Alessio Fabiani
> Founder/Technical Lead
> GeoSolutions S.A.S.
> Via di Montramito 3/A
> 55054 Massarosa
> phone: +39 0584 962313 <+39%200584%20962313>
> fax: +39 0584 1660272 <+39%200584%20166%200272>
> mob: +39 331 6233686 <+39%20331%20623%203686>
> AVVERTENZE AI SENSI DEL D.Lgs. 196/2003
> Le informazioni contenute in questo messaggio di posta elettronica e/o
> nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il
> loro utilizzo è consentito esclusivamente al destinatario del messaggio,
> per le finalità indicate nel messaggio stesso. Qualora riceviate questo
> messaggio senza esserne il destinatario, Vi preghiamo cortesemente di
> darcene notizia via e-mail e di procedere alla distruzione del messaggio
> stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso,
> divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od
> utilizzarlo per finalità diverse, costituisce comportamento contrario ai
> principi dettati dal D.Lgs. 196/2003.
> The information in this message and/or attachments, is intended solely for
> the attention and use of the named addressee(s) and may be confidential or
> proprietary in nature or covered by the provisions of privacy act
> (Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection
> Code).Any use not in accord with its purpose, any disclosure, reproduction,
> copying, distribution, or either dissemination, either whole or partial, is
> strictly forbidden except previous formal approval of the named
> addressee(s). If you are not the intended recipient, please contact
> immediately the sender by telephone, fax or e-mail and delete the
> information in this message that has been received in error. The sender
> does not give any warranty or accept liability as the content, accuracy or
> completeness of sent messages and accepts no responsibility for changes
> made after they were sent or for other risks which arise as a result of
> e-mail transmission, viruses, etc.
> On Mon, Dec 18, 2017 at 9:30 PM, LM Admin <skeenamaps at gmail.com> wrote:
>> I understand that the Geoserver data directory is different in 2.6 from
>> 2.4. However, the only problem seems to be that the layers are not visible
>> to public users. Is there a way to replace only the layer permissions on
>> the layers imported with the Geonode / Geoserver 2.4 data directory?
>> Or is it possible to copy just the layer info from the 2.4 data directory
>> into the 2.6 data directory? I'm not exactly clear on how to do this,
>> information referencing layers and styles seems to be in many places.
>> On Fri, Dec 15, 2017 at 3:02 PM, LM Admin <skeenamaps at gmail.com> wrote:
>>> Thank you for the suggestions. Should I be using this guide to setup
>>> Oauth? http://docs.geonode.org/en/master/tutorials/admin/geoserver_
>>> Oauth parameters seem to be set correctly. ./manage.py sync_geofence
>>> did not fix the issue, however.
>>> On Fri, Dec 15, 2017 at 2:41 PM, Francesco Bartoli <xbartolone at gmail.com
>>> > wrote:
>>>> GeoServer data dir is partially different so just copying wouldn’t
>>>> help. I think there should be a backup/restore procedure but I haven’t
>>>> tried it yet, maybe Paolo and Alessio can help here
>>>> Il giorno 15/dic/2017, alle ore 20:58, LM Admin <skeenamaps at gmail.com>
>>>> ha scritto:
>>>> > Hi all,
>>>> > I recently upgraded a client's map portal from Geonode 2.4 to 2.6. I
>>>> copied the db and updated to the 2.6 schema using manage.py --fake-initial,
>>>> and updatemaplayerip. I also copied the entire Geoserver data directory.
>>>> When logged in as a registered user, maps and layers work fine. However, as
>>>> an anonymous user (not logged in), none of the layers render correctly in
>>>> Geoserver--instead I get error tiles of class
>>>> olTileImage.olImageLoadError. In Geonode, all of these layers are set to
>>>> > However, new layers that I upload display correctly for both
>>>> registered and anonymous users. So the permission issue is limited to
>>>> layers imported from Geonode 2.4. Given the change in Geoserver versions,
>>>> and the change in authentication, is copying the entire Geoserver data
>>>> directory the right thing to do? Or am I missing a step?
>>>> > Thank you,
>>>> > LM
>>>> > _______________________________________________
>>>> > geonode-devel mailing list
>>>> > geonode-devel at lists.osgeo.org
>>>> > https://lists.osgeo.org/mailman/listinfo/geonode-devel
>> geonode-devel mailing list
>> geonode-devel at lists.osgeo.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the geonode-devel