Yes, it is correct, you have to import the certificate you see in
the JENKINS_HOME/saml-sp-metadata.xml file(or in the URL you marked in the
screenshot) in your IdP
El viernes, 13 de noviembre de 2020 a las 21:05:07 UTC+1,
david...@gmail.com escribió:
> Thanks all for the replies.
>
> I have
Thanks all for the replies.
I have generated a new JKS via the following command (had different values):
$JAVA_HOME/bin/keytool -genkeypair -alias saml-key -keypass \
-keystore /path/to/saml-key.jks -storepass \
-keyalg RSA -keysize 2048 -validity 3650
I then pointed in Jenkins UI to the
the result is the same you have a private key and a certificate that you
have to import in the Keystore, This Keystore is the one you have to
configure in the SAML plugin
El domingo, 8 de noviembre de 2020 a las 20:26:50 UTC+1, david...@gmail.com
escribió:
> Thank you for reply.
>
> If we
Thank you for reply.
If we are using encryption, does it means that typically when starting with
Jenkins SAML setup (e.g. ADFS) we are first creating certificate and
keypair via keytool (which will be stored in saml-jenkins-keystore.jks) and
then uploading it to ADFS, or are we first starting
This Keystore is automatically created if you do not configure encryption,
the Pac4j needs a key to work even though you do not use encryption. So in
general if you do not use sign or encryption in the SAML messages (not
related to TLS) you do need to configure anything this file will be used
Hello,
What is the correct way to renew an expired certificate
(JENKINS_HOME/saml-jenkins-keystore.jks) which is used for SAML Plugin
please?
https://github.com/jenkinsci/saml-plugin
In that process, what is the purpose of saml-jenkins-keystore.xml (e.g. is
it generated every time a new
