From c1ef527b0bb0b6c8f3e65e1f371932faa32bc87c Mon Sep 17 00:00:00 2001 From: "grafana-delivery-bot[bot]" <132647405+grafana-delivery-bot[bot]@users.noreply.github.com> Date: Tue, 15 Aug 2023 16:59:51 +0200 Subject: [PATCH] [v9.5.x] Docs: correct SAML docs (#73284) Docs: correct SAML docs (#73281) Correct SAML docs (cherry picked from commit 2848be90355d77e446c783fd339a7f4d49ed1199) Co-authored-by: Ieva --- .../configure-authentication/saml/index.md | 12 ++---------- 1 file changed, 2 insertions(+), 10 deletions(-) diff --git a/docs/sources/setup-grafana/configure-security/configure-authentication/saml/index.md b/docs/sources/setup-grafana/configure-security/configure-authentication/saml/index.md index 2a065e0537c..94689dec26d 100644 --- a/docs/sources/setup-grafana/configure-security/configure-authentication/saml/index.md +++ b/docs/sources/setup-grafana/configure-security/configure-authentication/saml/index.md @@ -108,17 +108,9 @@ An example of how to generate a self-signed certificate and private key that's v $ openssl req -x509 -newkey rsa:4096 -keyout key.pem -out cert.pem -days 365 -nodes​ ``` -Base64-encode the cert.pem and key.pem files: -(-w0 switch is not needed on Mac, only for Linux) +The generated `key.pem` and `cert.pem` files are then used for certificate and private_key. -```sh -$ base64 -w0 key.pem > key.pem.base64 -$ base64 -w0 cert.pem > cert.pem.base64 -``` - -The base64-encoded values (`key.pem.base64, cert.pem.base64` files) are then used for certificate and private_key. - -The keys you provide should look like: +The key you provide should look like: ``` -----BEGIN PRIVATE KEY-----