From 820ff01cf9453574c215fae5083299fe5dca21a5 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Jo=C3=A3o=20Palet?= Date: Wed, 25 Oct 2023 15:55:49 +0200 Subject: [PATCH] Revert "Add disclaimer to key flow doc (#73)" This reverts commit 9ec45e6be8e8bb069f55c0415ce551b01b2a0286. --- README.md | 3 --- templates/index.md.tmpl | 2 -- 2 files changed, 5 deletions(-) diff --git a/README.md b/README.md index d4e65dc5..76cb1ca0 100644 --- a/README.md +++ b/README.md @@ -34,7 +34,6 @@ When setting up authentication, the provider will always try to use the key flow ## Key flow To use the key flow, you need to have a service account key and an RSA key-pair. - To configure it, follow this steps: The following instructions assume that you have created a service account and assigned it the necessary permissions, e.g. project.owner. @@ -43,8 +42,6 @@ To configure it, follow this steps: - You can create your own RSA key-pair or have the Portal generate one for you. - **Disclaimer:** as of now, creation of a service account key in the Portal is only available in DEV and QA environments. You can use this flow in these environments by setting the fields `token_custom_endpoint` and `jwks_custom_endpoint` to the corresponding endpoints in the provider block. - 2. Save the content of the service account key and the corresponding private key by copying them or saving them in a file. **Hint:** If you have generated the RSA key-pair using the Portal, you can save the private key in a PEM encoded file by downloading the service account key as a PEM file and using `openssl storeutl -keys > private.key` to extract the private key from the service account key. diff --git a/templates/index.md.tmpl b/templates/index.md.tmpl index d2f7620a..e5925a42 100644 --- a/templates/index.md.tmpl +++ b/templates/index.md.tmpl @@ -42,8 +42,6 @@ To configure it, follow this steps: - You can create your own RSA key-pair or have the Portal generate one for you. -**Disclaimer:** as of now, creation of a service account key in the Portal is only available in DEV and QA environments. You can use this flow in these environments by setting the fields `token_custom_endpoint` and `jwks_custom_endpoint` to the corresponding endpoints in the provider block. - 2. Save the content of the service account key and the corresponding private key by copying them or saving them in a file. **Hint:** If you have generated the RSA key-pair using the Portal, you can save the private key in a PEM encoded file by downloading the service account key as a PEM file and using `openssl storeutl -keys > private.key` to extract the private key from the service account key.