You have to enable Auth Request Signature setting into encryption settings. 
Also, keep in mind that if you do not configure a keystore with a certificate 
you are using an auto generated certificate that it is valid for a year

Auth Request Signature - Enable signature of the Redirect Binding Auth Request, 
If you enable it the encryption and signing key would available in the SP 
metadata file and URL (JENKINS_URL/securityRealm/metadata).

Encryption - If your provider requires encryption or signing, you can specify 
the keystore details here that should be used. If you do not specify a 
keystore, the plugin would create one with a key that is valid for a year, this 
key would be recreate when it expires, by default the key is not exposed in the 
SP metadata if you do not enable signing.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" 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-users/2464a496-147a-4b86-bbc2-9674b9566028%40googlegroups.com.

Reply via email to