Hello all, I have been using Jenkins happily for a while now but I have out grown my server. I'm working on migrating to a new one with more space and some slightly better security (https via Apache front end, no Anonymous access, integrated into the rest of our Apache fronted infrastructure, etc). Since I am disallowing anonymous access, and I use JNLP for my windows slaves, I have to use the -jnlpCredentials options to get the agents to talk back to the server.
That all works well for the vast majority of my slaves. However, I have about a half dozen slaves that are not controlled by me and the entire dev community has access to the console to debug issues on those machines (they run the in depth integration tests). Needless to say I do NOT want to put my normal credentials in the jenkins-slave.xml on those machines. Also getting IT to create a general account in AD just for the slaves would be... trying at best. Given that I am using the Active Directory plugin as my Security Realm, is there any way to also create a local user in Jenkins that I could use for this generic JNLP access? -Jim NOTICE: All information in and attached to this email may be proprietary, confidential, privileged and otherwise protected from improper or erroneous disclosure. If you are not the sender's intended recipient, you are not authorized to intercept, read, print, retain, copy, forward, or disseminate this message.
