Dmytro Pishchukhin's picture

result is 404

Andy Korol's picture

Just ran into the same prob. My solution was to use the securityRealm from 12.0 - from now on the config is at /var/lib/jenkins/config.xml.

The old style was

<securityRealm class="">

Additionaly there have to be an according user configured by creating the folders users, myusername and a user config under /var/lib/jenkins/users/myusername/config.xml.

The content for a test user with pass test would be:

<?xml version='1.0' encoding='UTF-8'?>
  <fullName>test jenkins</fullName>
          <owner class="hudson.model.MyViewsProperty" reference="../../.."/>
          <properties class="hudson.model.View$PropertyList"/>
    <>      <passwordHash>#jbcrypt:$2a$10$razd3L1aXndFfBNHO95aj.IVrFydsxkcQCcLmujmFQzll3hcUrY7S</passwordHash>

Hope that helps!

julakali's picture

This worked for me.

It seems like the security realm was changed to PAM - which doesnt work..

Why does nobody fix this issue? makes the turnkey jenkins distribution unusable.

Alon Swartz's picture

Thanks for reporting this. I've added the issue to the tracker:

I've discovered that the root cause of the PAM authenticatin error is that the Jenkins plugins are not loading (including the PAM plugin)

The reason they are not loading is due to filesystem permissions.  The plugin directory is owned by root instead of being owned by jenkins.

To fix it:

  1. log-in or ssh to the server as root
  2. cd to /var/lib/jenkins
  3. execute: chown jenkins:nogroup plugins
  4. Restart jenkins (or reboot the server)

You should now be able to log-in as admin with the password that was set at first boot.

Jochem's picture

Want to confirm that this is the case after launching a jenkins 12.1 appliance. Provided administrator user and password fail to login and making the jenkins appliance not useable from the hub.

Jeremy Davis's picture

It's just that you'll need to log in via SSH (or SFTP or Webmin) and make the required changes as per the workaround above.

The only note is that you may need to adjust permissions (assuming that you use the root account to edit the files). Perhaps check their permissions prior to anything else!? ('ls -la /path/to/files') then chmod/chown them as appropriate...

yevgen's picture

Thank you John Palmer.

chown works beautifully.

Add new comment