You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+36Lines changed: 36 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -389,6 +389,22 @@ $settings = array (
389
389
*/
390
390
// 'certFingerprint' => '',
391
391
// 'certFingerprintAlgorithm' => 'sha1',
392
+
393
+
/* In some scenarios the IdP uses different certificates for
394
+
* signing/encryption, or is under key rollover phase and
395
+
* more than one certificate is published on IdP metadata.
396
+
* In order to handle that the toolkit offers that parameter.
397
+
* (when used, 'x509cert' and 'certFingerprint' values are
398
+
* ignored).
399
+
*/
400
+
// 'x509certMulti' => array(
401
+
// 'signing' => array(
402
+
// 0 => '<cert1-string>',
403
+
// ),
404
+
// 'encryption' => array(
405
+
// 0 => '<cert2-string>',
406
+
// )
407
+
// ),
392
408
),
393
409
);
394
410
```
@@ -1095,6 +1111,26 @@ You should be able to workaround this by configuring your server so that it is a
1095
1111
Or by using the method described on the previous section.
1096
1112
1097
1113
1114
+
### SP Key rollover ###
1115
+
1116
+
If you plan to update the SP x509cert and privateKey you can define the new x509cert as $settings['sp']['x509certNew'] and it will be
1117
+
published on the SP metadata so Identity Providers can read them and get ready for rollover.
1118
+
1119
+
1120
+
### IdP with multiple certificates ###
1121
+
1122
+
In some scenarios the IdP uses different certificates for
1123
+
signing/encryption, or is under key rollover phase and more than one certificate is published on IdP metadata.
1124
+
1125
+
In order to handle that the toolkit offers the $settings['idp']['x509certMulti'] parameter.
1126
+
1127
+
When that parameter is used, 'x509cert' and 'certFingerprint' values will be ignored by the toolkit.
1128
+
1129
+
The 'x509certMulti' is an array with 2 keys:
1130
+
- 'signing'. An array of certs that will be used to validate IdP signature
1131
+
- 'encryption' An array with one unique cert that will be used to encrypt data to be sent to the IdP
1132
+
1133
+
1098
1134
### Replay attacks ###
1099
1135
1100
1136
In order to avoid replay attacks, you can store the ID of the SAML messages already processed, to avoid processing them twice. Since the Messages expires and will be invalidated due that fact, you don't need to store those IDs longer than the time frame that you currently accepting.
0 commit comments