Skip to content

Commit ff6e4d5

Browse files
committed
Clarify the use of the certFingerprint
1 parent 508ce6f commit ff6e4d5

1 file changed

Lines changed: 6 additions & 2 deletions

File tree

README.md

Lines changed: 6 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -250,13 +250,17 @@ This is the settings.json file:
250250
// Public x509 certificate of the IdP
251251
"x509cert": "<onelogin_connector_cert>"
252252
/*
253-
* Instead of use the whole x509cert you can use a fingerprint
253+
* Instead of use the whole x509cert you can use a fingerprint in
254+
* order to validate a SAMLResponse.
254255
* (openssl x509 -noout -fingerprint -in "idp.crt" to generate it,
255-
* or add for example the -sha256 , -sha384 or -sha512 parameter)
256+
* or add for example the -sha256 , -sha384 or -sha512 parameter)
256257
*
257258
* If a fingerprint is provided, then the certFingerprintAlgorithm is required in order to
258259
* let the toolkit know which algorithm was used. Possible values: sha1, sha256, sha384 or sha512
259260
* 'sha1' is the default value.
261+
*
262+
* Notice that if you want to validate any SAML Message sent by the HTTP-Redirect binding, you
263+
* will need to provide the whole x509cert.
260264
*/
261265
// 'certFingerprint' => '',
262266
// 'certFingerprintAlgorithm' => 'sha1',

0 commit comments

Comments
 (0)