I have a similar but different issue. The active directory was upgraded properly to 1.27, but I also lost all jenkins admin rights ( There is no "Manage Jenkins" in the web page ).

$ cat /home/jenkins/plugins/active-directory/META-INF/MANIFEST.MF
Manifest-Version: 1.0
Archiver-Version: Plexus Archiver
Created-By: Apache Maven
Built-By: kohsuke
Build-Jdk: 1.6.0_26
Extension-Name: active-directory
Implementation-Title: active-directory
Implementation-Version: 1.27
Group-Id: org.jenkins-ci.plugins
Short-Name: active-directory
Long-Name: Jenkins Active Directory plugin
Url: http://wiki.jenkins-ci.org/display/JENKINS/Active+Directory+Plugin
Plugin-Version: 1.27
Hudson-Version: 1.403
Jenkins-Version: 1.403
Plugin-Developers: Kohsuke Kawaguchi:kohsuke:

I'll try to revert back to 1.26 to see if that helps.

If it helps, I am using project matrix authorisation

<authorizationStrategy class="hudson.security.ProjectMatrixAuthorizationStrategy">
<permission>hudson.model.Computer.Configure:salvojo</permission>
<permission>hudson.model.Computer.Connect:salvojo</permission>
<permission>hudson.model.Computer.Create:salvojo</permission>
<permission>hudson.model.Computer.Delete:salvojo</permission>
<permission>hudson.model.Computer.Disconnect:salvojo</permission>
<permission>hudson.model.Hudson.Administer:salvojo</permission>
< ...snip ...>

Confirmed that restoring the active directory plug-in back to 1.26 restored my admin rights, and the "Manage Jenkins" link is now displayed again.

I have the same behavior. (After upgrading, all admin users lost their privileged rights.)

However, I might have a clue, whats going on:

• With "Active Directory" plugin version 1.26: Jenkins shows my username in the top bar next to the logout-button.
• With "Active Directory" plugin version 1.27: Jenkins shows my realname (in the form of "lastname, firstname") in the top bar next to the logout-button.
• With "Active Directory" plugin version 1.27: Jenkins lists two users that seem to belong to me. One with my username as Jenkins user id (as with version 1.26), the other with my realname (in the form of "lastname, firstname").
• With all "Active Directory" plugin versions: No matter what, I still can only login to Jenkins with my username, not with my realname (in the form of "lastname, firstname").

After manually editing jenkins' config.xml in the filesystem - by copying all the permission-related lines with my username and replacing the username with realname ("lastname, firstname") - I am able to get my admin rights back.

I assume, something got mixed up in version 1.27, so that wrong fields are read from the "Active Directory" database and the realname accidentally becomes the Jenkins user id.

I updated the subject of this issue to reflect that the issue occurs on a successful upgrade to 1.27

Deniz is right ... I saw under /home/jenkins/users .... not the network user ID, but the full name of the user.

I have the same issue. I worked around it by going into config.xml and "Camel-Casing" all the user names. For example, each permission with the name "jacob.robertson" I changed to "Jacob.Robertson" and then restarted Jenkins. It worked.

I'm not sure what's going on... After making the fix I described above, I updated Jenkins to the latest LTS (1.447.1). At that time my permissions broke once again, and I had to fix config.xml to make my name all lower-case to get my permissions to show up.

Can everyone experiencing this issue vote for this ? There are currently only 2 votes. There should not bee a need to change anything in config.xml ( e.g. changing from the domain user ID to the user's real name ) when upgrading the plug-in.

Same problem here...
Hope the fix will be done quickly

Just experienced the same problem. We're also using Matrix security. 1.26 works fine, upgrading to 1.27 causes loss of admin rights. Reverted to 1.26 with no changes to config.xml and admin rights are back.

Even more info...

Depending on whether I login by typing "Jacob.Robertson" or "jacob.robertson" it will give me different permissions, but in both cases it will properly authenticate me.

No user rights are granted, not just loss of Admin. Only anonymous rights are granted.
Jenkins ver. 1.447.1

Argh. My 8b4c00a79201b605908d5d8983a7c719b0d645ff must have caused this. Fixing this now.

Rolled back. Fixed for 1.28.

Code changed in jenkins
User: Kohsuke Kawaguchi
Path:
src/main/java/hudson/plugins/active_directory/ActiveDirectoryUnixAuthenticationProvider.java
http://jenkins-ci.org/commit/active-directory-plugin/15a8a87bc333a12ead447425075df3bdafd7625c
Log:
[FIXED JENKINS-13650] Revert "JENKINS-12607 canonicalize the name."

This reverts commit 8b4c00a79201b605908d5d8983a7c719b0d645ff.

Compare: https://github.com/jenkinsci/active-directory-plugin/compare/e8943e7...15a8a87

In 1.27, because of the 8b4c00a7 change mentioned above, Jenkins was logging users into their canonical names, like "Kohsuke Kawaguchi", instead of their user names, like "kkawaguchi". Most authorization strategies record users by their user names, so of course such change results in the permission losses.

1.28 restores the previous behaviour. This unfortunately means for those who modified config.xml for 1.27 would have to redo that one more time. My apologies.

Integrated in plugins_active-directory #63
[FIXED JENKINS-13650] Revert "JENKINS-12607 canonicalize the name." (Revision 15a8a87bc333a12ead447425075df3bdafd7625c)

Result = SUCCESS
Kohsuke Kawaguchi :
Files :

• src/main/java/hudson/plugins/active_directory/ActiveDirectoryUnixAuthenticationProvider.java

Confirmed that 1.28 fixed this issue.

Closing based on the last comment.