No, but we also do not use https for our master. I had to disable some secure CSRF token setting in settings.conf or the LDAP auth would not work. Without this setting, lava would just redirect me to the front-page on successful logins without any errors and no valid sign-in.

On Mar 2, 2018 06:13, Conrad Djedjebi <conrad.djedjebi@linaro.org> wrote:
Hi Magnus Olsson,

Have you experienced issues regarding CSRF token? 

After migrating from LAVA 2016 to LAVA 2018, did your first login into your server return the following :




?

Regards,

Le 2 mars 2018 05:47, "Magnus Olsson" <magnus@minimum.se> a écrit :
We recently upgraded our master from an old 2016.11 to 2018.2. After about a week of fixing migration issues things are starting to work again. 2018.2 is so far a good release, the only open issue we have left is the broken csv export that breaks our tools for generating external reports (https://projects.linaro.org/browse/LAVA-1253)


On Mar 1, 2018 22:49, Conrad Djedjebi <conrad.djedjebi@linaro.org> wrote:
>
> Good morning LAVA users,
>
> I would like to know if there is someone among the LAVA users who installed his own LAVA 2018 master instance ?
>
> Is everyone here using the LAVA LAB master instance available here :  https://validation.linaro.org ? 
>
> Am I the only one who is installing his own LAVA 2018 master instance?
>
>
> Best regards,