From edd12fa358c97759ceb5801b52063b5c05214626 Mon Sep 17 00:00:00 2001 From: Darragh Bailey Date: Mon, 9 May 2016 15:35:46 +0100 Subject: [PATCH] Update docs that JJB is not the cause of CSRF issues Has been incorrectly reported that JJB has issues with CSRF, however that has been supported by python-jenkins, which JJB uses, and has been working for sometime. However other infra components are known to have issues with CSRF being enabled in Jenkins. Change-Id: I0a3b22f8aadbce06e9417c42a4666d2198d08642 Story: 2000556 --- doc/source/jenkins.rst | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/doc/source/jenkins.rst b/doc/source/jenkins.rst index 643a289ba0..24f70c8165 100644 --- a/doc/source/jenkins.rst +++ b/doc/source/jenkins.rst @@ -109,7 +109,8 @@ hand: #. Configure the OpenID plugin for your SSO site (e.g. Launchpad) -#. Do not set CSRF protection - that breaks Jenkins job builder. +#. Do not set CSRF protection - that causes problems with various components + such as nodepool and swift log uploader. #. Login.