Whenever the token is updated, the webhook is regenerated. This allow us to ensure that the provided token has needed api scope. Given you have a GitLab project integrated to Tuleap with a project access token, go to GitLab and revoke the token. 1. Create a new one with only `read_api` access scope. Go to Tuleap, open the modal to update the token. The token is accepted in the first step, but refused at the confirmation step. 2. Revoke the token, create a new one with `api` scope. Go to Tuleap, open the modal to update the token. The token is accepted and saved in the database. On GitLab the hook used to allow communication to Tuleap has been regenerated (you may need to check SSL verification configuration). Integration still works (comments, cross references, …) Part of story #17182: reference tuleap artifacts in gitlab merge requests Change-Id: If30c41f2711d021827ed898f33a6cdd47826883b

+147 −18

Author

Nicolas Terray (nterray) 2021-01-25 18:29

Committer

Nicolas Terray (nterray) 2021-01-26 11:28

Hash 2774f1f6452d7c75cd206023642cbebdec61dbd0

Parent 68259d0d89cbb1bd7941e6595bdf044edb7970f7

Reference git #tuleap/stable/2774f1f6452d7c75cd206023642cbebdec61dbd0