Hi We have a user called Service_Build which is used for issuing Jenkins CLI commands (either in bash or in Jenkins). This user is defined in Active Directory, which is what we use for authentication. So normally, I can log in as this user and I have administrator rights in Jenkins.
I followed the documentation in the Jenkins wiki and (with help from Rob Mandeville) managed to authenticate the Service_Build user with public/private key credentials. So that part works well. However, it looks like Jenkins is still trying to authenticate that user with Active Directory, because the user is locked in Active Directory after a number of CLI commands (eight in our case). Should I have created the private key using the Active Directory password? Or how can I prevent that Active Directory locking? Best regards, Eric
