At least start by reading https://github.com/jenkinsci/reverse-proxy-auth-plugin/pull/40 and https://github.com/jenkinsci/ldap-plugin/pull/49.
https://github.com/jenkinsci/reverse-proxy-auth-plugin/pull/37 would perhaps help. The root problem is the lack of a general way in Jenkins to compose security realms—often to get “fallback” functionality (e.g. to log in while the primary system is down), but more pertinently here, to delegate calculation of granted authorities (“groups”) to another system such as LDAP while controlling the user identifier (login). `reverse-proxy-auth` therefore includes its own LDAP call layer because it cannot delegate that to the `ldap` plugin, so to migrate to Spring Security you have a lot of code to rewrite. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr2%2B-hEi_a0Ppbgty6WQgoRUPofFuR3ARqBQOyR9NcCwgw%40mail.gmail.com.
