As stated in the answer, the fastest way to get around this would be to completely disable security by making the following change to your Jenkins config.xml file:
<useSecurity>true</useSecurity>
After rebooting your Jenkins instance, you can return to the administration page and install everything there.
An alternative solution for this is mentioned here , which should accomplish what you want while maintaining the security of your Jenkins instance (thereby making it a more ideal solution). Instead, you updated the passwordHash section of your Jenkins config.xml file:
<passwordHash>
The passwordHash section of the config.xml file is a child tag in <hudson.security.HudsonPrivateSecurityRealm_-Details> .
You will again need to restart Jenkins after this change is made, and you must log in using the password 'test'. Of course, you could provide your own hash of a different password, which would be appropriate.
lax1089
source share