• Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • ldap-plugin
    • None

      I've setup LDAP authentication which works fine. The only issue I have is that only the user id is properly populated. Instead of populating the name with e.g. the displayName attribute from the LDAP object, the user id is copied over to the name. Apparently there is no UserNameResolver available for LDAP. So I've created a plugin implementing this extension point but it's never invoked. Also there is no reference in the code.

          [JENKINS-14936] UserNameResolver extension never invoked

          Yves Schumann added a comment -

          Any news or plans on this? Would be great if this could be solved...

          Yves Schumann added a comment - Any news or plans on this? Would be great if this could be solved...

          evernat added a comment -

          There is no jenkins plugin in this issue, except a promise in the description.
          So resolving as incomplete.

          evernat added a comment - There is no jenkins plugin in this issue, except a promise in the description. So resolving as incomplete.

          Yves Langisch added a comment -

          Just make a simple plugin which implements the UserNameResolver extension point (http://javadoc.jenkins-ci.org/hudson/tasks/UserNameResolver.html). Your plugin will never be invoked during login or whenever.

          Yves Langisch added a comment - Just make a simple plugin which implements the UserNameResolver extension point ( http://javadoc.jenkins-ci.org/hudson/tasks/UserNameResolver.html ). Your plugin will never be invoked during login or whenever.

          evernat added a comment -

          In that case, it would be better to have a reproductible test case (zip of a project) and to know how to test it.

          evernat added a comment - In that case, it would be better to have a reproductible test case (zip of a project) and to know how to test it.

          Daniel Beck added a comment -

          evernat: This has nothing to do with a project. It's a global extension point that's simply unused in all of Jenkins, while suggesting that this is how additional functionality could be provided.

          Daniel Beck added a comment - evernat: This has nothing to do with a project. It's a global extension point that's simply unused in all of Jenkins, while suggesting that this is how additional functionality could be provided.

          Daniel Beck added a comment -

          LDAP security realm is in a plugin.

          AFAICT, the extension point needs to be invoked by security realms not able to provide a full name, which might explain why it's not actually used in core.

          Daniel Beck added a comment - LDAP security realm is in a plugin. AFAICT, the extension point needs to be invoked by security realms not able to provide a full name, which might explain why it's not actually used in core.

          evernat added a comment -

          @danielbeck
          Given that the reporter has not provided a reproductible test case with a test plugin,
          and given that you say that this extension point needs to be invoked by security realms, in a never seen case,
          then I would suggest to resolve this issue as invalid.

          The subject can be better asked on the dev list, if ever needed.

          evernat added a comment - @ danielbeck Given that the reporter has not provided a reproductible test case with a test plugin, and given that you say that this extension point needs to be invoked by security realms, in a never seen case, then I would suggest to resolve this issue as invalid. The subject can be better asked on the dev list, if ever needed.

          Daniel Beck added a comment -

          Well, it has been discussed on the dev list (in Aug 2012). Vincent Latombe wrote in response to this issue's reporter:

          it looks like UserNameResolver is never called from anywhere (at least from core). IMO it should be called in User#get(String, boolean).

          I definitely think this issue has merit – I'm just not sure where it needs to be resolved.

          Daniel Beck added a comment - Well, it has been discussed on the dev list (in Aug 2012). Vincent Latombe wrote in response to this issue's reporter: it looks like UserNameResolver is never called from anywhere (at least from core). IMO it should be called in User#get(String, boolean). I definitely think this issue has merit – I'm just not sure where it needs to be resolved.

          evernat added a comment -

          Among everyone, vlatombe has merit ("la tombe", or "the grave", (, hopefully the guy is different).

          Anyway, just a single intuition from vlatombe in August 2012 is not enough in 2014.
          I still think that this should be closed, if there is no more than this.
          Please.

          evernat added a comment - Among everyone, vlatombe has merit ("la tombe", or "the grave", (, hopefully the guy is different). Anyway, just a single intuition from vlatombe in August 2012 is not enough in 2014. I still think that this should be closed, if there is no more than this. Please.

            Unassigned Unassigned
            ylangisc Yves Langisch
            Votes:
            2 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated: