Skip to content

Commit 72165de

Browse files
committed
Clarify the use of the certFingerprint
1 parent d4be3be commit 72165de

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
@@ -255,13 +255,17 @@ This is the settings.json file:
255255
// Public x509 certificate of the IdP
256256
"x509cert": "<onelogin_connector_cert>"
257257
/*
258-
* Instead of use the whole x509cert you can use a fingerprint
258+
* Instead of use the whole x509cert you can use a fingerprint in order to
259+
* validate a SAMLResponse.
259260
* (openssl x509 -noout -fingerprint -in "idp.crt" to generate it,
260-
* or add for example the -sha256 , -sha384 or -sha512 parameter)
261+
* or add for example the -sha256 , -sha384 or -sha512 parameter)
261262
*
262263
* If a fingerprint is provided, then the certFingerprintAlgorithm is required in order to
263264
* let the toolkit know which algorithm was used. Possible values: sha1, sha256, sha384 or sha512
264265
* 'sha1' is the default value.
266+
*
267+
* Notice that if you want to validate any SAML Message sent by the HTTP-Redirect binding, you
268+
* will need to provide the whole x509cert.
265269
*/
266270
// 'certFingerprint' => '',
267271
// 'certFingerprintAlgorithm' => 'sha1',

0 commit comments

Comments
 (0)