Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

EI Documentation update regarding API Token usage in Jenkins authentication for subscription #520

Merged
merged 1 commit into from
Jan 18, 2022
Merged

EI Documentation update regarding API Token usage in Jenkins authentication for subscription #520

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions wiki/triggering-jenkins-jobs.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -28,6 +28,9 @@ authentication type works. BASIC_AUTH can also be used.
### userName & password
The username and password Eiffel Intelligence will use in headers of the HTTP
request when sending a notification via HTTP POST.
As improved CSRF protection provided since Jenkins version 2.176.2, it is recommended that to set this Password/Token field
as an API token and not Jenkins user password. Click [here](https://www.jenkins.io/doc/upgrade-guide/2.176/#SECURITY-626)
to see Jenkins upgrade guides regarding this improvement.

### notificationMeta
Which url to use for the HTTP POST request. This url contains parameters to
Expand Down