You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What Operating System are you using (both controller, and any agents involved in the problem)?
Linux
Reproduction steps
Install fresh Jenkins
Install proxy with NTLM/KERBEROS/BASIC auth methods
Create AWS IAM role, IAM user and setup AssumeRole in this plugin
Set proxy in Jenkins
Set proxy account locking rules to small number
Try to use AWS credentials, see Jenkins log. Lot of messages regarding NTLM/Kerberos realm/domain missing will be logged, proxy account will become locked out
Results
Expected result:
For 99% of proxies, BASIC auth method is enough. Set ProxyAuthenticationMethods in AWS JAVA SDK accordingly / add configuration option to plugin. When uninitialized, it uses the following list - SPNEGO, KERBEROS, NTLM, DIGEST, BASIC. At least for Kerberos and NTLM there are missing fields in proxy setting, leading to errors in jenkins log and possible proxy account lockout, when hard account locking rules are set.
Actual result:
Actually we have problems when using this plugin with our proxy, leading to account lockouts.
The text was updated successfully, but these errors were encountered:
Version report
Jenkins and plugins versions report:
Reproduction steps
Results
Expected result:
For 99% of proxies, BASIC auth method is enough. Set ProxyAuthenticationMethods in AWS JAVA SDK accordingly / add configuration option to plugin. When uninitialized, it uses the following list - SPNEGO, KERBEROS, NTLM, DIGEST, BASIC. At least for Kerberos and NTLM there are missing fields in proxy setting, leading to errors in jenkins log and possible proxy account lockout, when hard account locking rules are set.
Actual result:
Actually we have problems when using this plugin with our proxy, leading to account lockouts.
The text was updated successfully, but these errors were encountered: