-
Bug
-
Resolution: Not A Defect
-
Minor
-
None
On integrating Jenkins with IDaptive for SAML SSO, it errors out with 'No Valid Crumb' post the SAML response.
Jenkins Version: 2.332.1
SAML Plugin Version: 2.298.vc7a_2b_3958628
The Jenkins log shows the following error:
2022-06-17 10:45:28.632+0000 [id=9] INFO o.o.x.a.AlgorithmRegistry#index: Algorithm failed runtime support check, will not be usable: http://www.w3.org/2001/04/xmlenc#kw-aes192 2022-06-17 10:45:28.632+0000 [id=9] INFO o.o.x.a.AlgorithmRegistry#checkCipherSupportedKeyLength: Cipher algorithm 'http://www.w3.org/2001/04/xmlenc#kw-aes256' is not supported, its key length 256 exceeds Cipher max key length 128 2022-06-17 10:45:28.633+0000 [id=9] INFO o.o.x.a.AlgorithmRegistry#index: Algorithm failed runtime support check, will not be usable: http://www.w3.org/2001/04/xmlenc#kw-aes256 2022-06-17 10:45:28.633+0000 [id=9] INFO o.o.x.a.AlgorithmRegistry#checkCipherSupportedKeyLength: Cipher algorithm 'http://www.w3.org/2001/04/xmlenc#kw-tripledes' is not supported, its key length 192 exceeds Cipher max key length 128
We do have other Jenkins servers (multiple of them) that are integrated with Idaptive in the same fashion and are working appropriately. It is only this one server.
I will provide the details of one of the working ones.
The working Jenkins server has
Jenkins Version: 2.332.3
SAML Plugin version: 2.297.v1a_dff8e51f90
