Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-14936

UserNameResolver extension never invoked

XMLWordPrintable

    • 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 Langisch created issue -

          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.
          evernat made changes -
          Resolution New: Incomplete [ 4 ]
          Status Original: Open [ 1 ] New: Resolved [ 5 ]

          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.
          Yves Langisch made changes -
          Resolution Original: Incomplete [ 4 ]
          Status Original: Resolved [ 5 ] New: Reopened [ 4 ]

          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.
          Daniel Beck made changes -
          Component/s New: ldap [ 17122 ]
          Component/s Original: core [ 15593 ]

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

              Created:
              Updated: