summaryrefslogtreecommitdiff
path: root/doc/ci/triggers/README.md
diff options
context:
space:
mode:
authorMatija Čupić <matteeyah@gmail.com>2019-03-12 03:37:05 +0000
committerEvan Read <eread@gitlab.com>2019-03-12 03:37:05 +0000
commit9756a6cc0ca8dbe5587c665724fde218ff5fdf6f (patch)
treee2567581c63748481217c6ea93f01ac8445ee86c /doc/ci/triggers/README.md
parent54df720039616f413a8820d12d0f1ff5d08c3daf (diff)
downloadgitlab-ce-9756a6cc0ca8dbe5587c665724fde218ff5fdf6f.tar.gz
Resolve "A lot of Trigger Token is Accessible from Internet because of the Documentation"
Diffstat (limited to 'doc/ci/triggers/README.md')
-rw-r--r--doc/ci/triggers/README.md9
1 files changed, 6 insertions, 3 deletions
diff --git a/doc/ci/triggers/README.md b/doc/ci/triggers/README.md
index bceccf4d40d..398b017277f 100644
--- a/doc/ci/triggers/README.md
+++ b/doc/ci/triggers/README.md
@@ -17,6 +17,12 @@ The following methods of authentication are supported.
A unique trigger token can be obtained when [adding a new trigger](#adding-a-new-trigger).
+DANGER: **Danger:**
+Passing plain text tokens in public projects is a security issue. Potential
+attackers can impersonate the user that exposed their trigger token publicly in
+their `.gitlab-ci.yml` file. Use [variables](../variables/README.md#variables)
+to protect trigger tokens.
+
## Adding a new trigger
You can add a new trigger by going to your project's
@@ -53,9 +59,6 @@ The action is irreversible.
>
> - Valid refs are only the branches and tags. If you pass a commit SHA as a ref,
> it will not trigger a job.
-> - If your project is public, passing the token in plain text is probably not the
-> wisest idea, so you might want to use a
-> [variable](../variables/README.md#variables) for that purpose.
To trigger a job you need to send a `POST` request to GitLab's API endpoint: