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
+10-10Lines changed: 10 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -151,7 +151,7 @@ If our environment requires sign or encrypt support, the certs folder may contai
151
151
* sp.crt The public cert of the SP
152
152
* sp.key The private key of the SP
153
153
154
-
Or also we can provide those data in the setting file at the ``X.509cert`` and the ``privateKey`` JSON parameters of the ``sp`` element.
154
+
Or also we can provide those data in the setting file at the ``x509cert`` and the ``privateKey`` JSON parameters of the ``sp`` element.
155
155
156
156
Sometimes we could need a signature on the metadata published by the SP, in this case we could use the X.509 cert previously mentioned or use a new X.509 cert: ``metadata.crt`` and ``metadata.key``.
157
157
@@ -161,7 +161,7 @@ publish that X.509 certificate on Service Provider metadata.
161
161
If you want to create self-signed certs, you can do it at the https://www.samltool.com/self_signed_certs.php service, or using the command:
// Usually X.509cert and privateKey of the SP are provided by files placed at
267
+
// Usually X.509 cert and privateKey of the SP are provided by files placed at
268
268
// the certs folder. But we can also provide them with the following parameters
269
269
"x509cert":"",
270
270
"privateKey":""
@@ -310,7 +310,7 @@ This is the ``settings.json`` file:
310
310
* But take in mind that the fingerprint, is a hash, so at the end is open to a collision attack that can end on a signature validation bypass,
311
311
* that why we don't recommend it use for production environments.
312
312
*
313
-
* (openssl X.509 -noout -fingerprint -in "idp.crt" to generate it,
313
+
* (openssl x509 -noout -fingerprint -in "idp.crt" to generate it,
314
314
* or add for example the -sha256 , -sha384 or -sha512 parameter)
315
315
*
316
316
* If a fingerprint is provided, then the certFingerprintAlgorithm is required in order to
@@ -343,7 +343,7 @@ This is the ``settings.json`` file:
343
343
}
344
344
```
345
345
346
-
In addition to the required settings data (IdP, SP), extra settings can be defined in `advanced_settings.json`:
346
+
In addition to the required settings data (idp, sp), extra settings can be defined in `advanced_settings.json`:
347
347
348
348
```javascript
349
349
{
@@ -865,7 +865,7 @@ else:
865
865
866
866
### SP Key rollover ###
867
867
868
-
If you plan to update the SP ``X.509cert`` and ``privateKey`` you can define the new ``X.509cert`` as ``settings['sp']['X.509certNew']`` and it will be
868
+
If you plan to update the SP ``x509cert`` and ``privateKey`` you can define the new ``x509cert`` as ``settings['sp']['x509certNew']`` and it will be
869
869
published on the SP metadata so Identity Providers can read them and get ready for rollover.
870
870
871
871
@@ -874,11 +874,11 @@ published on the SP metadata so Identity Providers can read them and get ready f
874
874
In some scenarios the IdP uses different certificates for
875
875
signing/encryption, or is under key rollover phase and more than one certificate is published on IdP metadata.
876
876
877
-
In order to handle that the toolkit offers the ``settings['idp']['X.509certMulti']`` parameter.
877
+
In order to handle that the toolkit offers the ``settings['idp']['x509certMulti']`` parameter.
878
878
879
-
When that parameter is used, ``X.509cert`` and ``certFingerprint`` values will be ignored by the toolkit.
879
+
When that parameter is used, ``x509cert`` and ``certFingerprint`` values will be ignored by the toolkit.
880
880
881
-
The ``X.509certMulti`` is an array with 2 keys:
881
+
The ``x509certMulti`` is an array with 2 keys:
882
882
-``signing``: An array of certs that will be used to validate IdP signature
883
883
-``encryption``: An array with one unique cert that will be used to encrypt data to be sent to the IdP.
884
884
@@ -1026,7 +1026,7 @@ A class that contains functionality related to the metadata of the SP
1026
1026
1027
1027
****builder*** Generates the metadata of the SP based on the settings.
1028
1028
****sign_metadata*** Signs the metadata with the key/cert provided.
1029
-
****add_X.509_key_descriptors*** Adds the X.509 descriptors (sign/encryption) to the metadata
1029
+
****add_x509_key_descriptors*** Adds the X.509 descriptors (sign/encryption) to the metadata
0 commit comments