• Icon: Task Task
    • Resolution: Fixed
    • Icon: Major Major
    • ldap-plugin
    • None
    • 733.vd3700c27b_043

      LDAP plugin currently delivers WEB-INF/lib/spring-security-ldap-5.7.2.jar in its JPI file. This is incompatible with Spring Security 6.x, which requires version 6.x of spring-security-ldap. Unfortunately, this plugin cannot be prepared in advance of the transition, since doing so would break compatibility with Spring Security 5.x and existing cores. So on the same day a core weekly is released with EE 9 / Spring Security 6.x, LDAP plugin should be updated to depend on that weekly and to embed spring-security-ldap 6.x, and a release should be performed on that day. The adoption of that release of LDAP plugin should take place in lockstep with the adoption of the abovementioned weekly in any BOMs, including jenkinsci/bom as well as any proprietary BOMs.

      The code change is trivial, simply adopting the latest weekly release as the jenkins.version and rebuilding, and has been prototyped at https://github.com/basil/ldap-plugin/tree/jakarta. The tricky part of this ticket is not the code change, but the release coordination. The assignee of this ticket must ensure they are able to do a release of the LDAP plugin with these changes on the very same day the corresponding core weekly release goes out, and adapt BOMs like jenkinsci/bom accordingly.

          [JENKINS-73279] Adapt LDAP plugin for Spring Security 6.x

          Basil Crow created issue -
          Basil Crow made changes -
          Description Original: LDAP plugin currently delivers {{WEB-INF/lib/spring-security-ldap-5.7.2.jar}} in its JPI file. This is incompatible with Spring Security 6.x, which requires version 6.x of {{spring-security-ldap}}. Unfortunately, this plugin cannot be prepared in advance of the transition, since doing so would break compatibility with Spring Security 5.x and existing cores. So on the same day a core weekly is released with EE 9 / Spring Security 6.x, LDAP plugin should be updated to depend on that weekly and to embed {{spring-security-ldap}} 6.x, and a release should be performed on that day. The adoption of that release of LDAP plugin should take place in lockstep with the adoption of the abovementioned weekly in any BOMs, including {{jenkinsci/bom}} as well as any proprietary BOMs.

          The code change is trivial, simply adopting the latest weekly release as the {{jenkins.version}} and rebuilding, and has been prototyped at https://github.com/basil/ldap-plugin/tree/jakarta. The tricky part of this ticket is not the code change, but the release coordination.
          New: LDAP plugin currently delivers {{WEB-INF/lib/spring-security-ldap-5.7.2.jar}} in its JPI file. This is incompatible with Spring Security 6.x, which requires version 6.x of {{{}spring-security-ldap{}}}. Unfortunately, this plugin cannot be prepared in advance of the transition, since doing so would break compatibility with Spring Security 5.x and existing cores. So on the same day a core weekly is released with EE 9 / Spring Security 6.x, LDAP plugin should be updated to depend on that weekly and to embed {{spring-security-ldap}} 6.x, and a release should be performed on that day. The adoption of that release of LDAP plugin should take place in lockstep with the adoption of the abovementioned weekly in any BOMs, including {{jenkinsci/bom}} as well as any proprietary BOMs.

          The code change is trivial, simply adopting the latest weekly release as the {{jenkins.version}} and rebuilding, and has been prototyped at [https://github.com/basil/ldap-plugin/tree/jakarta]. The tricky part of this ticket is not the code change, but the release coordination. The assignee of this ticket must ensure they are able to do a release of the LDAP plugin with these changes on the very same day the corresponding core weekly release goeso ut.
          Basil Crow made changes -
          Description Original: LDAP plugin currently delivers {{WEB-INF/lib/spring-security-ldap-5.7.2.jar}} in its JPI file. This is incompatible with Spring Security 6.x, which requires version 6.x of {{{}spring-security-ldap{}}}. Unfortunately, this plugin cannot be prepared in advance of the transition, since doing so would break compatibility with Spring Security 5.x and existing cores. So on the same day a core weekly is released with EE 9 / Spring Security 6.x, LDAP plugin should be updated to depend on that weekly and to embed {{spring-security-ldap}} 6.x, and a release should be performed on that day. The adoption of that release of LDAP plugin should take place in lockstep with the adoption of the abovementioned weekly in any BOMs, including {{jenkinsci/bom}} as well as any proprietary BOMs.

          The code change is trivial, simply adopting the latest weekly release as the {{jenkins.version}} and rebuilding, and has been prototyped at [https://github.com/basil/ldap-plugin/tree/jakarta]. The tricky part of this ticket is not the code change, but the release coordination. The assignee of this ticket must ensure they are able to do a release of the LDAP plugin with these changes on the very same day the corresponding core weekly release goeso ut.
          New: LDAP plugin currently delivers {{WEB-INF/lib/spring-security-ldap-5.7.2.jar}} in its JPI file. This is incompatible with Spring Security 6.x, which requires version 6.x of {{{}spring-security-ldap{}}}. Unfortunately, this plugin cannot be prepared in advance of the transition, since doing so would break compatibility with Spring Security 5.x and existing cores. So on the same day a core weekly is released with EE 9 / Spring Security 6.x, LDAP plugin should be updated to depend on that weekly and to embed {{spring-security-ldap}} 6.x, and a release should be performed on that day. The adoption of that release of LDAP plugin should take place in lockstep with the adoption of the abovementioned weekly in any BOMs, including {{jenkinsci/bom}} as well as any proprietary BOMs.

          The code change is trivial, simply adopting the latest weekly release as the {{jenkins.version}} and rebuilding, and has been prototyped at [https://github.com/basil/ldap-plugin/tree/jakarta]. The tricky part of this ticket is not the code change, but the release coordination. The assignee of this ticket must ensure they are able to do a release of the LDAP plugin with these changes on the very same day the corresponding core weekly release goes out.
          Basil Crow made changes -
          Description Original: LDAP plugin currently delivers {{WEB-INF/lib/spring-security-ldap-5.7.2.jar}} in its JPI file. This is incompatible with Spring Security 6.x, which requires version 6.x of {{{}spring-security-ldap{}}}. Unfortunately, this plugin cannot be prepared in advance of the transition, since doing so would break compatibility with Spring Security 5.x and existing cores. So on the same day a core weekly is released with EE 9 / Spring Security 6.x, LDAP plugin should be updated to depend on that weekly and to embed {{spring-security-ldap}} 6.x, and a release should be performed on that day. The adoption of that release of LDAP plugin should take place in lockstep with the adoption of the abovementioned weekly in any BOMs, including {{jenkinsci/bom}} as well as any proprietary BOMs.

          The code change is trivial, simply adopting the latest weekly release as the {{jenkins.version}} and rebuilding, and has been prototyped at [https://github.com/basil/ldap-plugin/tree/jakarta]. The tricky part of this ticket is not the code change, but the release coordination. The assignee of this ticket must ensure they are able to do a release of the LDAP plugin with these changes on the very same day the corresponding core weekly release goes out.
          New: LDAP plugin currently delivers {{WEB-INF/lib/spring-security-ldap-5.7.2.jar}} in its JPI file. This is incompatible with Spring Security 6.x, which requires version 6.x of {{{}spring-security-ldap{}}}. Unfortunately, this plugin cannot be prepared in advance of the transition, since doing so would break compatibility with Spring Security 5.x and existing cores. So on the same day a core weekly is released with EE 9 / Spring Security 6.x, LDAP plugin should be updated to depend on that weekly and to embed {{spring-security-ldap}} 6.x, and a release should be performed on that day. The adoption of that release of LDAP plugin should take place in lockstep with the adoption of the abovementioned weekly in any BOMs, including {{jenkinsci/bom}} as well as any proprietary BOMs.

          The code change is trivial, simply adopting the latest weekly release as the {{jenkins.version}} and rebuilding, and has been prototyped at [https://github.com/basil/ldap-plugin/tree/jakarta]. The tricky part of this ticket is not the code change, but the release coordination. The assignee of this ticket must ensure they are able to do a release of the LDAP plugin with these changes on the very same day the corresponding core weekly release goes out, and adapt BOMs like {{jenkinsci/bom}} accordingly.
          Basil Crow made changes -
          Link New: This issue is blocking JENKINS-73283 [ JENKINS-73283 ]
          Basil Crow made changes -
          Link New: This issue depends on JENKINS-73278 [ JENKINS-73278 ]
          Basil Crow made changes -
          Status Original: Open [ 1 ] New: In Progress [ 3 ]
          Basil Crow made changes -
          Status Original: In Progress [ 3 ] New: In Review [ 10005 ]
          Basil Crow made changes -
          Remote Link New: This issue links to "jenkinsci/ldap-plugin#5 (Web Link)" [ 29711 ]
          Basil Crow made changes -
          Remote Link New: This issue links to "jenkinsci/ldap-plugin#285 (Web Link)" [ 29966 ]
          Basil Crow made changes -
          Assignee New: Basil Crow [ basil ]

            basil Basil Crow
            basil Basil Crow
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: