-
-
Notifications
You must be signed in to change notification settings - Fork 755
Optionally use an api token instead of password to download plugins #398
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.
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
base: master
Are you sure you want to change the base?
Conversation
… task does not happen in time
|
This pr has been marked 'stale' due to lack of recent activity. If there is no further activity, the issue will be closed in another 30 days. Thank you for your contribution! Please read this blog post to see the reasons why I mark issues as stale. |
|
This pr has been marked 'stale' due to lack of recent activity. If there is no further activity, the issue will be closed in another 30 days. Thank you for your contribution! Please read this blog post to see the reasons why I mark issues as stale. |
Please note it would be ideal to merge this only after this is approved in community.general repo: ansible-collections/community.general#9130
We noticed when installing SSO on our Jenkins instance that we run into errors with authorization to download plugins because we cannot get a crumb. One way around this is to use an api token instead of password to download plugins and use the force_basic_auth param (that param is not properly integrated into the jenkins_plugin module to create a basic auth header at this time, see PR above).
Groovy script to create an API token only on start up happens when jenkins_use_api_token param is true (default is false) and it is expected that the user would provide the value of the intended API token controlled by jenkins_api_token.