Skip to content

Commit

Permalink
Revert "Add disclaimer to key flow doc (#73)"
Browse files Browse the repository at this point in the history
This reverts commit 9ec45e6.
  • Loading branch information
joaopalet authored Oct 25, 2023
1 parent fe566d3 commit 820ff01
Show file tree
Hide file tree
Showing 2 changed files with 0 additions and 5 deletions.
3 changes: 0 additions & 3 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand All @@ -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 <path/to/sa_key_pem_file> > private.key` to extract the private key from the service account key.
Expand Down
2 changes: 0 additions & 2 deletions templates/index.md.tmpl
Original file line number Diff line number Diff line change
Expand Up @@ -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 <path/to/sa_key_pem_file> > private.key` to extract the private key from the service account key.
Expand Down

0 comments on commit 820ff01

Please sign in to comment.