Skip to content

Commit b1f7fbe

Browse files
committed
Clarify the use of the fingerprint
Close SAML-Toolkits#87
1 parent 82b9c97 commit b1f7fbe

File tree

1 file changed

+6
-2
lines changed

1 file changed

+6
-2
lines changed

README.md

Lines changed: 6 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -325,13 +325,17 @@ $settings = array (
325325
// Public x509 certificate of the IdP
326326
'x509cert' => '',
327327
/*
328-
* Instead of use the whole x509cert you can use a fingerprint
328+
* Instead of use the whole x509cert you can use a fingerprint in order to
329+
* validate a SAMLResponse.
329330
* (openssl x509 -noout -fingerprint -in "idp.crt" to generate it,
330331
* or add for example the -sha256 , -sha384 or -sha512 parameter)
331332
*
332333
* If a fingerprint is provided, then the certFingerprintAlgorithm is required in order to
333334
* let the toolkit know which algorithm was used. Possible values: sha1, sha256, sha384 or sha512
334335
* 'sha1' is the default value.
336+
*
337+
* Notice that if you want to validate any SAML Message sent by the HTTP-Redirect binding, you
338+
* will need to provide the whole x509cert.
335339
*/
336340
// 'certFingerprint' => '',
337341
// 'certFingerprintAlgorithm' => 'sha1',
@@ -1341,4 +1345,4 @@ validation, the userdata and the nameID will be available, using `getNameId()` o
13411345
`getAttributes()` we obtain them.
13421346

13431347
Since the version 1 of the php toolkit does not support SLO we don't show how
1344-
handle SLO in this demo-old.
1348+
handle SLO in this demo-old.

0 commit comments

Comments
 (0)