[GeoNode-users] Geonode 2.6 and Geoserver integration
giovanifronza at gmail.com
Mon Mar 6 09:45:16 PST 2017
Following the link sent by Alesio (
I noticed that there was no application configured for Django Oauth
Toolkit. I created application and configured Client ID and Secret
accordingly. Now everything is fine.
Thank you guys!
2017-03-06 11:37 GMT-03:00 Alessio Fabiani <alessio.fabiani at geo-solutions.it
> In that case I'd suggest you to follow those simple steps
> Best Regards,
> Alessio Fabiani.
> GeoServer Professional Services from the experts!
> Visit http://goo.gl/it488V for more information.
> Ing. Alessio Fabiani
> github <https://github.com/afabiani?tab=overview>
> Founder/Technical Lead
> GeoSolutions S.A.S.
> Via di Montramito 3/A
> 55054 Massarosa (LU)
> 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, Mar 6, 2017 at 3:35 PM, Giovani Fronza <giovanifronza at gmail.com>
>> I get the code from https://github.com/GeoNode/geo
>> node/archive/debian/2.6.0+alpha1.zip, unziped and run '$ sudo pip
>> install -e .'
>> Geoserver was get from $ sudo paver setup, copied from downloaded to
>> 2017-03-06 11:27 GMT-03:00 Francesco Bartoli <xbartolone at gmail.com>:
>>> Hi Giovani,
>>> How did you perform the installation? If you rely on ppa this
>>> configuration is done automatically. Please be careful that only testing
>>> release is available at the moment since we are managing with few bugs
>>> before the official stable.
>>> Hope this helps
>>> Sent from Nylas Pro
>>> the most powerful email app for work
>>> On mar 6 2017, at 3:12 pm, Giovani Fronza <giovanifronza at gmail.com>
>>>> Hello list!
>>>> I'm trying to use version 2.6 for a production server on the local
>>>> network. It looks like everything is ok with the geonode configuration for
>>>> local address 10.108.128.38, except for integration with geoserver.
>>>> So I tried to adjust the settings for authentication in the geoserver
>>>> by replacing the localhost:8000 parameters with my local address
>>>> 10.108.128.38, resulting in the following configuration:
>>>> [image: Imagem inline 2]
>>>> I still can not access the geoserver in authenticated mode from the
>>>> geonode. When I try to perform authentication using the geonode logo button
>>>> on the geoserver interface I get the following notification:
>>>> Error: invalid_request
>>>> Invalid client_id parameter value.
>>>> What could be wrong here? How to get valid values for Client ID and
>>>> Client Secret for Oauth2 authentication?
>> geonode-users mailing list
>> geonode-users at lists.osgeo.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the geonode-users