[GeoNode-devel] [GeoNode-users] GeoNode Credentials Login

[Julierme Pinheiro]

You can see here http://iamgeo.com.br/

Kind regards

Julierme

On Tue, Mar 26, 2019 at 6:56 PM Julierme Pinheiro <
juliermeopensourcedeveloper at gmail.com> wrote:

> And no Caps Lock on.
>
> On Tue, Mar 26, 2019 at 6:55 PM Julierme Pinheiro <
> juliermeopensourcedeveloper at gmail.com> wrote:
>
>> And geoserver response while liging in:
>>
>> Invalid username/password combination.
>>
>> On Tue, Mar 26, 2019 at 6:53 PM Julierme Pinheiro <
>> juliermeopensourcedeveloper at gmail.com> wrote:
>>
>>> Hi Francesco,
>>>
>>> Thank you very much for your reply. Look at this response. I did not do
>>> any change at all:
>>>
>>> Forbidden (403)
>>>
>>> CSRF verification failed. Request aborted.
>>>
>>> You are seeing this message because this site requires a CSRF cookie
>>> when submitting forms. This cookie is required for security reasons, to
>>> ensure that your browser is not being hijacked by third parties.
>>>
>>> If you have configured your browser to disable cookies, please re-enable
>>> them, at least for this site, or for 'same-origin' requests.
>>> Help
>>>
>>> Reason given for failure:
>>>
>>>     CSRF cookie not set.
>>>
>>>
>>> In general, this can occur when there is a genuine Cross Site Request
>>> Forgery, or when Django's CSRF mechanism
>>> <https://docs.djangoproject.com/en/1.11/ref/csrf/> has not been used
>>> correctly. For POST forms, you need to ensure:
>>>
>>>    - Your browser is accepting cookies.
>>>    - The view function passes a request to the template's render
>>>    <https://docs.djangoproject.com/en/dev/topics/templates/#django.template.backends.base.Template.render>
>>>    method.
>>>    - In the template, there is a {% csrf_token %} template tag inside
>>>    each POST form that targets an internal URL.
>>>    - If you are not using CsrfViewMiddleware, then you must use
>>>    csrf_protect on any views that use the csrf_token template tag, as
>>>    well as those that accept the POST data.
>>>    - The form has a valid CSRF token. After logging in in another
>>>    browser tab or hitting the back button after a login, you may need to
>>>    reload the page with the form, because the token is rotated after a login.
>>>
>>> You're seeing the help section of this page because you have DEBUG =
>>> True in your Django settings file. Change that to False, and only the
>>> initial error message will be displayed.
>>>
>>> You can customize this page using the CSRF_FAILURE_VIEW setting.
>>> I appreciated your reply.
>>>
>>> Julierme
>>>
>>> On Tue, Mar 26, 2019 at 6:37 PM Francesco Bartoli <xbartolone at gmail.com>
>>> wrote:
>>>
>>>> Hi Julierme,
>>>>
>>>> I’m right now on a geonode-project based code and the login is working
>>>> well for me.
>>>>
>>>> Francesco
>>>> Il 26 mar 2019, 22:30 +0100, Julierme Pinheiro <
>>>> juliermeopensourcedeveloper at gmail.com>, ha scritto:
>>>>
>>>> Dear users and developers,
>>>>
>>>> I just installed via Docker a brand new master geonode-project on a
>>>> Ubuntu18.04lTS server and after installation I could not do a login either
>>>> through geonode and geoserver default credentials:
>>>> admin admin
>>>> admin geoserver.
>>>>
>>>> Has anyone faced the same issue? Did the default credentials change?
>>>>
>>>> I appreciated your time.
>>>>
>>>> Kind regards
>>>>
>>>> Julierme
>>>>
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> geonode-users mailing list
>>>> geonode-users at lists.osgeo.org
>>>> https://lists.osgeo.org/mailman/listinfo/geonode-users
>>>>
>>>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/geonode-devel/attachments/20190326/52d6d648/attachment.html>