Hi Misagh, I have been able to comply to the SHA-256 requirement by creating certificates manually:
- Firstly I created the files saml-signing-cert-SAML2Client.crt, saml-signing-cert-SAML2Client.key, saml-signing-cert-SAML2Client.pem with openssl - Then I created samlKeystore.jks with keytool - Finally, since sp-metadata.xml should contain the public certificate, I copied the content of the .pem certificate where relevant in the sp-metadata.xml file Thanks, Giacomo On Thursday, March 25, 2021 at 5:27:26 PM UTC+1 Misagh Moayyed wrote: > Or generate everything manually, if the software can't do it for you, yet. > > On Thu, Mar 25, 2021 at 8:26 PM Misagh <[email protected]> wrote: > > > > > Can anyone tell me what values are allowed for that parameter? > > > > Not the relevant setting. The setting you want to modify should > > control the generation of the certificate; not what algorithms should > > be allowed/used during the metadata resolution process. > > > > ...and that setting is supported by pac4j-saml, but support for it has > > not been brought over to CAS. You're welcome to send a pull request to > > handle that part. > -- - Website: https://apereo.github.io/cas - Gitter Chatroom: https://gitter.im/apereo/cas - List Guidelines: https://goo.gl/1VRrw7 - Contributions: https://goo.gl/mh7qDG --- You received this message because you are subscribed to the Google Groups "CAS Community" 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/a/apereo.org/d/msgid/cas-user/1479dc81-72d6-4e7d-8450-73b7f5cf7738n%40apereo.org.
