Hi Remi,

Yep, setting those two to „false” did the trick. Thanks a lot!

From: Remi Duraffort [mailto:remi.duraffort@linaro.org]
Sent: Thursday, November 9, 2017 2:56 PM
To: Dragos Iorgulescu <Dragos.Iorgulescu@enea.com>
Cc: lava-users@lists.linaro.org
Subject: Re: [Lava-users] 403: Forbidden - CSRF verification failed (2017.10-1)

Hello,

I've you looked at this item in the documeantion https://staging.validation.linaro.org/static/docs/v2/pipeline-debug.html#using-localhost-or-non-https-instance-url ?

Cheers.

2017-11-09 13:31 GMT+01:00 Dragos Iorgulescu <Dragos.Iorgulescu@enea.com>:

Hi everyone!

I have recently upgraded our production server to 2017.10-1. Whenever anyone tries to login in the WEB UI, either the “403: Forbidden – CSRF verification failed” error is returned, or no error at all (for the latter, the default LAVA page is shown again, but with no login info).

I also tried creating a new superuser from the CLI. That worked, but I can’t use it to logon via the WEB UI, so I guess this has nothing to do with the user accounts stored in LAVA.

Is this triggered by a change in Django/LAVA?

Kind regards,

Dragoș

_______________________________________________
Lava-users mailing list
Lava-users@lists.linaro.org
https://lists.linaro.org/mailman/listinfo/lava-users

--

Rémi Duraffort

LAVA Team