Update SAMl plugin to use current Spring Security release
14 views
Skip to first unread message
kuisathaverat
Feb 12, 2021, 7:15:56 AM2/12/21
to jenkin...@googlegroups.com
Hi,
Due to Upgrade Acegi Security to the latest Spring Security release(https://issues.jenkins.io/browse/JENKINS-5303),
I updated the SAML plugin to use the new Sprint Security version and pac4j 3.9.0(https://issues.jenkins.io/browse/JENKINS-63350 and https://github.com/jenkinsci/saml-plugin/pull/90) ,
this requires bumping the shibboleth library. Shibboleth library is not in the maven central repository
Due to Upgrade Acegi Security to the latest Spring Security release(https://issues.jenkins.io/browse/JENKINS-5303),
I updated the SAML plugin to use the new Sprint Security version and pac4j 3.9.0(https://issues.jenkins.io/browse/JENKINS-63350 and https://github.com/jenkinsci/saml-plugin/pull/90) ,
this requires bumping the shibboleth library. Shibboleth library is not in the maven central repository
due to security reasons (https://wiki.shibboleth.net/confluence/display/DEV/Use+of+Maven+Central),
because of that, I have open an issue to mirror/copy the Shibboleth library repository (https://issues.jenkins.io/browse/INFRA-2809)
The issue here is that I cannot merge and release the SAML plugin with that change without resolve INFRA-2809
in one way or another, Could we find a solution for this?
--
Un Saludo
Iván Fernández Calvo
Reply all
Reply to author
Forward
0 new messages