Skip to content
Snippets Groups Projects
Commit 9a88312d authored by Tim van Dijen's avatar Tim van Dijen Committed by Thijs Kinkhorst
Browse files

Fix markdown

(cherry picked from commit 8a68ea27)
parent 55fdb7cb
No related branches found
No related tags found
No related merge requests found
...@@ -14,13 +14,16 @@ entity publishes metadata with two certificates in it. Meanwhile it continues to ...@@ -14,13 +14,16 @@ entity publishes metadata with two certificates in it. Meanwhile it continues to
5. Your SimpleSAMLphp now publishes metadata with only the new cert. Relying parties will refresh metadata and drop the old certificate, not trusting it anymore (or remove the old certificate from their config manually). This last step is essential to ensure that the old certificate is actually distrusted. 5. Your SimpleSAMLphp now publishes metadata with only the new cert. Relying parties will refresh metadata and drop the old certificate, not trusting it anymore (or remove the old certificate from their config manually). This last step is essential to ensure that the old certificate is actually distrusted.
## The steps ## The steps
### Create the new key and certificate ### Create the new key and certificate
First you must create the new key that you are going to use. First you must create the new key that you are going to use.
To create a self signed certificate, you may use the following command: To create a self signed certificate, you may use the following command:
cd cert ```bash
openssl req -newkey rsa:3072 -new -x509 -days 3652 -nodes -out new.crt -keyout new.pem cd cert
openssl req -newkey rsa:3072 -new -x509 -days 3652 -nodes -out new.crt -keyout new.pem
```
### Add the new key to SimpleSAMLphp ### Add the new key to SimpleSAMLphp
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment