[GeoNode-users] Help with geonodeAuthProvider configuration
Ivo Santos
ivojfs at gmail.com
Tue Jan 26 07:43:50 PST 2016
Ariel, thank you for sharing your experience. I am, of course, beginning to
think seriously on the reinstall hypothesis.
Alessio, the SLD URL on table "layers_style" was set to:
"<bound method Style.body_href of <geoserver.style.Style object at
0x7f07a6038d10>>";
"<bound method Style.body_href of <geoserver.style.Style object at
0x7efcb9dabed0>>";
"<bound method Style.body_href of <geoserver.style.Style object at
0x7fb0e4a65f90>>"
...
I tried to change it on every single layer to
http://atlas.example.com:8080/geoserver/rest/styles/general.sld and it's
working now.
Tested to upload a new layer and to put the "Default Polygon" as defaut
style and the same error occurs.
The new layer on the SLD URL appear again the same type of
"<bound method Style.body_href of <geoserver.style.Style object at
0x7fb0e4ec4690>>"
After changing to the same url as above, every logged user can open the
layers.
But when I try to create a new map an internal 500 error occurs:
- On *apache *log:
[Tue Jan 26 15:38:46.834380 2016] [authz_core:debug] [pid 8066]
mod_authz_core.c(802): [client 193.136.219.68:63432] AH01626: authorization
result of Require all granted: granted, referer:
http://atlas.example.com/maps/new?layer=geonode:conc42_wgs84
[Tue Jan 26 15:38:46.834414 2016] [authz_core:debug] [pid 8066]
mod_authz_core.c(802): [client 193.136.219.68:63432] AH01626: authorization
result of <RequireAny>: granted, referer:
http://atlas.example.com/maps/new?layer=geonode:conc42_wgs84
[Tue Jan 26 15:38:46.834524 2016] [authz_core:debug] [pid 8066]
mod_authz_core.c(802): [client 193.136.219.68:63432] AH01626: authorization
result of Require all granted: granted, referer:
http://atlas.example.com/maps/new?layer=geonode:conc42_wgs84
[Tue Jan 26 15:38:46.834536 2016] [authz_core:debug] [pid 8066]
mod_authz_core.c(802): [client 193.136.219.68:63432] AH01626: authorization
result of <RequireAny>: granted, referer:
http://atlas.example.com/maps/new?layer=geonode:conc42_wgs84
[Tue Jan 26 15:38:47.299144 2016] [core:error] [pid 8066] [client
193.136.219.68:63432] End of script output before headers: geonode.wsgi,
referer: http://atlas.example.com/maps/new?layer=geonode:conc42_wgs84
[Tue Jan 26 15:38:47.972265 2016] [core:notice] [pid 1516] AH00051: child
pid 10059 exit signal Segmentation fault (11), possible coredump in
/etc/apache2
- on *geoserver *log:
2016-01-26 15:28:37,071 WARN [yaml.CustomBeanWrapper] - MetaData: unknown
field 'footer' with value '{height=30,
items=[org.mapfish.print.config.layout.ColumnsBlock at 141dedd2]}'
2016-01-26 15:28:37,085 WARN [yaml.CustomBeanWrapper] - MainPage: Error
while writing '{height=30,
items=[org.mapfish.print.config.layout.ColumnsBlock at 141dedd2]}' to footer:
java.lang.IllegalArgumentException: argument type mismatch
[...]
2016-01-26 15:28:40,364 WARN [yaml.CustomBeanWrapper] - MetaData: unknown
field 'footer' with value '{height=30,
items=[org.mapfish.print.config.layout.ColumnsBlock at 35ef1451]}'
Thank you,
Regards,
Ivo
2016-01-26 8:47 GMT+00:00 Alessio Fabiani <alessio.fabiani at geo-solutions.it>
:
> Mmm, thinking ... maybe the issue is just the SLD URL stored on the DB.
>
> Try to change manually the geoserver URL on the table "layer_style" and
> see if it works.
>
> ==
> GeoServer Professional Services from the experts! Visit
> http://goo.gl/NWWaa2 for more information.
> ==
>
> Ing. Alessio Fabiani
> @alfa7691
> Founder/Technical Lead
>
> GeoSolutions S.A.S.
> Via Poggio alle Viti 1187
> 55054 Massarosa (LU)
> Italy
> phone: +39 0584 962313
> fax: +39 0584 1660272
> mob: +39 331 6233686
>
> http://www.geo-solutions.it
> http://twitter.com/geosolutions_it
>
> -------------------------------------------------------
>
> *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 Tue, Jan 26, 2016 at 5:10 AM, Ariel Cabezas <gerardoarielc at gmail.com>
> wrote:
>
>> Ivo,
>> I tell you my experience:
>> *(Does anyone have a clue of what is the problem? It seems the same
>> problem Ariel had in
>> November: https://lists.osgeo.org/pipermail/geonode-users/2015-November/001150.html
>> <https://lists.osgeo.org/pipermail/geonode-users/2015-November/001150.html>)*
>> My problems started when:
>> - Install GeoNode and default settings; upload some layers;
>> later,
>> - I did the steps to set GeoNode for Production
>> - I change the key geoserver from the web platform Geoserver without
>> changing the key in the file local_settings.py
>> then I tried to upload new data layers; and of course they began error
>> messages
>> and I could not go back to the settings. don't remember that changes
>> made.
>> mistakes were mine;
>> I had to reinstall GeoNode and could change the key geoserver without any
>> problem; and then load the data layers without problems too,
>> now everything works correctly
>> regards,
>> Ariel Cabezas
>>
>> 2016-01-25 19:28 GMT-03:00 Ivo Santos <ivojfs at gmail.com>:
>>
>>> Alessio,
>>>
>>> The same error occurs on both situations. It only depends of being
>>> logged to geonode or not. Do you think I should reinstall geonode and
>>> geoserver?
>>>
>>> Regards,
>>> Ivo
>>>
>>> 2016-01-25 17:47 GMT+00:00 Alessio Fabiani <
>>> alessio.fabiani at geo-solutions.it>:
>>>
>>>> Is your layer a raster or vectorial one?
>>>>
>>>> ==
>>>> GeoServer Professional Services from the experts! Visit
>>>> http://goo.gl/NWWaa2 for more information.
>>>> ==
>>>>
>>>> Ing. Alessio Fabiani
>>>> @alfa7691
>>>> Founder/Technical Lead
>>>>
>>>> GeoSolutions S.A.S.
>>>> Via Poggio alle Viti 1187
>>>> 55054 Massarosa (LU)
>>>> Italy
>>>> phone: +39 0584 962313
>>>> fax: +39 0584 1660272
>>>> mob: +39 331 6233686
>>>>
>>>> http://www.geo-solutions.it
>>>> http://twitter.com/geosolutions_it
>>>>
>>>> -------------------------------------------------------
>>>>
>>>> *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 Fri, Jan 22, 2016 at 4:06 PM, Ivo Santos <ivojfs at gmail.com> wrote:
>>>>
>>>>> Nevermind the last email. In my tests to try to solve the issue, I
>>>>> erased the trailing slash of the <baseUrl> on
>>>>> geonodeAuthProvider/config.xml.
>>>>>
>>>>> I am on the same point right now (I can't see the layers on
>>>>> geoexplorer only if any geonode user is logged on). Possibily is something
>>>>> like this error and I missed some slash or something like that.
>>>>>
>>>>> I tryed "DEBUG = TEMPLATE_DEBUG = True" on local_settings.py
>>>>>
>>>>> I am not sure if it helps, but the error that appears is:
>>>>>
>>>>> IndexError at /layers/geonode:teste
>>>>>
>>>>> list index out of range
>>>>>
>>>>> Request Method:GET
>>>>> Request URL:http://atlas.example.com/layers/geonode:teste
>>>>> Django Version:1.6.1
>>>>> Exception Type:IndexError
>>>>> Exception Value:
>>>>>
>>>>> list index out of range
>>>>>
>>>>> Exception
>>>>> Location:/usr/local/lib/python2.7/dist-packages/geonode/layers/models.py in
>>>>> absolute_url, line 68
>>>>> Python Executable:/usr/bin/python
>>>>> Python Version:2.7.6
>>>>> Python Path:
>>>>>
>>>>> ['/usr/lib/python2.7',
>>>>> '/usr/lib/python2.7/plat-x86_64-linux-gnu',
>>>>> '/usr/lib/python2.7/lib-tk',
>>>>> '/usr/lib/python2.7/lib-old',
>>>>> '/usr/lib/python2.7/lib-dynload',
>>>>> '/usr/local/lib/python2.7/dist-packages',
>>>>> '/usr/lib/python2.7/dist-packages',
>>>>> '/usr/lib/python2.7/dist-packages/PILcompat',
>>>>> '/usr/lib/pymodules/python2.7',
>>>>> '/var/www']
>>>>>
>>>>> Server time:Sex, 22 Jan 2016 08:59:55 -0600
>>>>>
>>>>>
>>>>> Error during template rendering
>>>>>
>>>>> In template
>>>>> /usr/local/lib/python2.7/dist-packages/geonode/layers/templates/layers/layer_detail.html,
>>>>> error at line *322*
>>>>>
>>>>>
>>>>>
>>>>> *<a href="{{ GEOSERVER_BASE_URL }}{{ style.absolute_url }}" >{{
>>>>> style.sld_title }}</a>*
>>>>>
>>>>>
>>>>>
>>>>> I can try to send the all file if some of you think it would be better.
>>>>>
>>>>>
>>>>> Thank you for your attention,
>>>>> Ivo
>>>>>
>>>>> 2016-01-22 13:20 GMT+00:00 Ivo Santos <ivojfs at gmail.com>:
>>>>>
>>>>>> Alessio,
>>>>>>
>>>>>> Thank you for the explanation about mod_wsgi. I think it wasn't the
>>>>>> situation. I tried the steps on that page who could be apllied and it's not
>>>>>> working. Inclusive, there was a step back. Now I am like before: the user
>>>>>> admin has to be logged to geoserver (and can't be logged on geonode) to be
>>>>>> able to see the layers on the geoexplorer.
>>>>>>
>>>>>> I am trying now the geoexplorer debug as described on the
>>>>>> documentation. It has to be something wrong on the configuration. But what?
>>>>>>
>>>>>> Thank you,
>>>>>> Ivo
>>>>>>
>>>>>> 2016-01-22 8:54 GMT+00:00 Alessio Fabiani <
>>>>>> alessio.fabiani at geo-solutions.it>:
>>>>>>
>>>>>>> Well, specifically mod_wsgi is an Apache HTTPD module. It allows you
>>>>>>> to create a virtual folder/host in order to proxy the GeoNode DJango
>>>>>>> application.
>>>>>>>
>>>>>>> If you see mod_wsgi errors on the Apache error logs, most probably
>>>>>>> there is something wrong, which usually can be a configuration issue or a
>>>>>>> Python exception.
>>>>>>>
>>>>>>> In the GeoNode official documentation there are several pages
>>>>>>> showing the steps for the correct configuration of GeoNode with mod_wsgi.
>>>>>>>
>>>>>>> One page which may be helpful on your case maybe this one:
>>>>>>>
>>>>>>>
>>>>>>> http://docs.geonode.org/en/latest/tutorials/admin/customize_lookfeel/customize/setup_admin.html#setup-admin
>>>>>>>
>>>>>>>
>>>>>>> ==
>>>>>>> GeoServer Professional Services from the experts! Visit
>>>>>>> http://goo.gl/NWWaa2 for more information.
>>>>>>> ==
>>>>>>>
>>>>>>> Ing. Alessio Fabiani
>>>>>>> @alfa7691
>>>>>>> Founder/Technical Lead
>>>>>>>
>>>>>>> GeoSolutions S.A.S.
>>>>>>> Via Poggio alle Viti 1187
>>>>>>> 55054 Massarosa (LU)
>>>>>>> Italy
>>>>>>> phone: +39 0584 962313
>>>>>>> fax: +39 0584 1660272
>>>>>>> mob: +39 331 6233686
>>>>>>>
>>>>>>> http://www.geo-solutions.it
>>>>>>> http://twitter.com/geosolutions_it
>>>>>>>
>>>>>>> -------------------------------------------------------
>>>>>>>
>>>>>>> *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 Thu, Jan 21, 2016 at 2:12 PM, Ivo Santos <ivojfs at gmail.com>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> It's not working on development mode.
>>>>>>>>
>>>>>>>> Sorry the (probably) dumb question, but how can I use mod_wsgi to
>>>>>>>> run GeonNode?
>>>>>>>> Maybe this info could help. The error that appears on apache when
>>>>>>>> the user is logged on geonode and tries to see a layer is:
>>>>>>>> mod_wsgi (pid=7536): Exception occurred processing WSGI script
>>>>>>>> '/var/www/geonode/wsgi/geonode.wsgi'.
>>>>>>>> [...]
>>>>>>>>
>>>>>>>> And I realized that:
>>>>>>>> if the user is logged he can't see the layers (Example:
>>>>>>>> http://atlas.example.com/layers/geonode%3Acom26_wgs84 ) .
>>>>>>>> if the user tries to create a new map (
>>>>>>>> http://atlas.example.com/layers/maps/new) the layers appear as
>>>>>>>> available and could be shown on the map.
>>>>>>>> But if the user tries to save the map with the layers on screen, it
>>>>>>>> gives a 500 error.
>>>>>>>>
>>>>>>>> Thank you in advance.
>>>>>>>>
>>>>>>>> Best regards,
>>>>>>>> Ivo
>>>>>>>>
>>>>>>>> 2016-01-21 13:01 GMT+00:00 Alessio Fabiani <
>>>>>>>> alessio.fabiani at geo-solutions.it>:
>>>>>>>>
>>>>>>>>> One more thing, if you are running GeoNode in development mode
>>>>>>>>> (paver start_django) it may not work when running the embedded geoserver.
>>>>>>>>>
>>>>>>>>> If is not yet like this, try using mod_wsgi to run GeoNode
>>>>>>>>>
>>>>>>>>> ==
>>>>>>>>> GeoServer Professional Services from the experts! Visit
>>>>>>>>> http://goo.gl/NWWaa2 for more information.
>>>>>>>>> ==
>>>>>>>>>
>>>>>>>>> Ing. Alessio Fabiani
>>>>>>>>> @alfa7691
>>>>>>>>> Founder/Technical Lead
>>>>>>>>>
>>>>>>>>> GeoSolutions S.A.S.
>>>>>>>>> Via Poggio alle Viti 1187
>>>>>>>>> 55054 Massarosa (LU)
>>>>>>>>> Italy
>>>>>>>>> phone: +39 0584 962313
>>>>>>>>> fax: +39 0584 1660272
>>>>>>>>> mob: +39 331 6233686
>>>>>>>>>
>>>>>>>>> http://www.geo-solutions.it
>>>>>>>>> http://twitter.com/geosolutions_it
>>>>>>>>>
>>>>>>>>> -------------------------------------------------------
>>>>>>>>>
>>>>>>>>> *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 Thu, Jan 21, 2016 at 1:30 PM, Ivo Santos <ivojfs at gmail.com>
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>>> Alessio,
>>>>>>>>>>
>>>>>>>>>> Thank you for your reply. I think that I did understand what you
>>>>>>>>>> were saying... After some improvements, geonode and geoserver are still
>>>>>>>>>> unable to communicate when a user is logged on geonode (this time,
>>>>>>>>>> independently of being logged on geoserver).
>>>>>>>>>>
>>>>>>>>>> On local_settings.py:
>>>>>>>>>>
>>>>>>>>>> # OGC (WMS/WFS/WCS) Server Settings
>>>>>>>>>> OGC_SERVER = {
>>>>>>>>>> 'default' : {
>>>>>>>>>> 'BACKEND' : 'geonode.geoserver',
>>>>>>>>>> 'LOCATION' : 'http://atlas.example.com:8080/geoserver/',
>>>>>>>>>> 'PUBLIC_LOCATION' : GEOSERVER_URL,
>>>>>>>>>> 'USER' : 'admin',
>>>>>>>>>> 'PASSWORD' : '*********************'
>>>>>>>>>>
>>>>>>>>>> [...]
>>>>>>>>>>
>>>>>>>>>> ALLOWED_HOSTS=['atlas.example.com']
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On geonodeAuthProvider/config.xml:
>>>>>>>>>>
>>>>>>>>>> <baseUrl>http://atlas.example.com/</baseUrl>
>>>>>>>>>>
>>>>>>>>>> Does anyone have a clue of what is the problem? It seems the same
>>>>>>>>>> problem Ariel had in November:
>>>>>>>>>> https://lists.osgeo.org/pipermail/geonode-users/2015-November/001150.html
>>>>>>>>>>
>>>>>>>>>> Best regards,
>>>>>>>>>> Ivo
>>>>>>>>>>
>>>>>>>>>> 2016-01-20 15:19 GMT+00:00 Alessio Fabiani <
>>>>>>>>>> alessio.fabiani at geo-solutions.it>:
>>>>>>>>>>
>>>>>>>>>>> The GeoNode/GeoServer security, right now, in order to work
>>>>>>>>>>> correctly needs both GeoNode and GeoServer exposed under the same domain
>>>>>>>>>>> (and the same port).
>>>>>>>>>>>
>>>>>>>>>>> Therefore if you expose GeoNode as http://mysite/ you must also
>>>>>>>>>>> expose GeoServer as http://mysite/geoserver
>>>>>>>>>>>
>>>>>>>>>>> The GeoNode authentication provider can be configured with
>>>>>>>>>>> http://localhost, I guess, but you must be sure that GeoServer
>>>>>>>>>>> is also exposed as http://localhost/geoserver.
>>>>>>>>>>>
>>>>>>>>>>> The rationale is that the GeoNodeSecurityClient looks for the
>>>>>>>>>>> AuthPrincipal from the cookies.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> ==
>>>>>>>>>>> GeoServer Professional Services from the experts! Visit
>>>>>>>>>>> http://goo.gl/NWWaa2 for more information.
>>>>>>>>>>> ==
>>>>>>>>>>>
>>>>>>>>>>> Ing. Alessio Fabiani
>>>>>>>>>>> @alfa7691
>>>>>>>>>>> Founder/Technical Lead
>>>>>>>>>>>
>>>>>>>>>>> GeoSolutions S.A.S.
>>>>>>>>>>> Via Poggio alle Viti 1187
>>>>>>>>>>> 55054 Massarosa (LU)
>>>>>>>>>>> Italy
>>>>>>>>>>> phone: +39 0584 962313
>>>>>>>>>>> fax: +39 0584 1660272
>>>>>>>>>>> mob: +39 331 6233686
>>>>>>>>>>>
>>>>>>>>>>> http://www.geo-solutions.it
>>>>>>>>>>> http://twitter.com/geosolutions_it
>>>>>>>>>>>
>>>>>>>>>>> -------------------------------------------------------
>>>>>>>>>>>
>>>>>>>>>>> *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 Wed, Jan 20, 2016 at 3:58 PM, Ivo Santos <ivojfs at gmail.com>
>>>>>>>>>>> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> Hi everyone,
>>>>>>>>>>>>
>>>>>>>>>>>> After several limiting issues concerning the configuration of
>>>>>>>>>>>> apache that I have to thank you especially to Simone for all the help and
>>>>>>>>>>>> guidance, I am now with a problem with the connection between geonode and
>>>>>>>>>>>> geoserver:
>>>>>>>>>>>>
>>>>>>>>>>>> If user as log in on geoserver but not on geonode, he can view
>>>>>>>>>>>> the layers.
>>>>>>>>>>>> If user is not loged on geoserver, he can not view the layers
>>>>>>>>>>>> and the error is:
>>>>>>>>>>>> 2016-01-20 14:39:59,947 WARN [geonode.security] - Error
>>>>>>>>>>>> connecting to the GeoNode server for authentication purposes
>>>>>>>>>>>> org.springframework.security.authentication.AuthenticationServiceException:
>>>>>>>>>>>> Communication with GeoNode failed (UsernamePasswordAuthenticationToken)
>>>>>>>>>>>>
>>>>>>>>>>>> If user is logged on both geonode and geoserver it gives a
>>>>>>>>>>>> internal error (500).
>>>>>>>>>>>>
>>>>>>>>>>>> Following this thread
>>>>>>>>>>>> <https://groups.google.com/forum/m/#!topic/geonode-users/84HvjbarPE8>I
>>>>>>>>>>>> tried to apply this doc
>>>>>>>>>>>> <https://github.com/GeoNode/geonode/commit/cc732e0a73c6d04d8f57fdf376dfb9a9848abd86>to
>>>>>>>>>>>> my installation but it didn't worked.
>>>>>>>>>>>> Does it have to remain like "http://localhost/" on both files
>>>>>>>>>>>> or should I substitute by "http://atlas.example.com" on both?
>>>>>>>>>>>> If you need more info please let me know.
>>>>>>>>>>>>
>>>>>>>>>>>> Thank you for all the help and patience for this newcomer,
>>>>>>>>>>>> regards,
>>>>>>>>>>>> Ivo
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> --
>>>>>>>>>>>> Ivo Santos
>>>>>>>>>>>>
>>>>>>>>>>>> _______________________________________________
>>>>>>>>>>>> geonode-users mailing list
>>>>>>>>>>>> geonode-users at lists.osgeo.org
>>>>>>>>>>>> http://lists.osgeo.org/mailman/listinfo/geonode-users
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> Ivo Santos
>>>>>>>>>>
>>>>>>>>>> _______________________________________________
>>>>>>>>>> geonode-users mailing list
>>>>>>>>>> geonode-users at lists.osgeo.org
>>>>>>>>>> http://lists.osgeo.org/mailman/listinfo/geonode-users
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Ivo Santos
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Ivo Santos
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Ivo Santos
>>>>>
>>>>> _______________________________________________
>>>>> geonode-users mailing list
>>>>> geonode-users at lists.osgeo.org
>>>>> http://lists.osgeo.org/mailman/listinfo/geonode-users
>>>>>
>>>>>
>>>>
>>>
>>>
>>> --
>>> Ivo Santos
>>>
>>> _______________________________________________
>>> geonode-users mailing list
>>> geonode-users at lists.osgeo.org
>>> http://lists.osgeo.org/mailman/listinfo/geonode-users
>>>
>>>
>>
>
--
Ivo Santos
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/geonode-users/attachments/20160126/7181ee10/attachment-0001.html>
More information about the geonode-users
mailing list