Added instructions on how to generate PEM keypair, needed by JWT authentication #2812
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Preview of modified filesPreview of modified Markdown: |
vidarl
changed the title
mnocon
reviewed
Jul 9, 2025
mnocon
reviewed
Jul 9, 2025
| php bin/console lexik:jwt:generate-keypair | ||
| ``` | ||
|
|
||
| The generated key pair will be stored in `config/jwt` |
There was a problem hiding this comment.
Suggested change
| The generated key pair will be stored in `config/jwt` | |
| The generated key pair will be stored in the `config/jwt`directory. |
Comment on lines
+159
to
+162
| In order to be able to store generate and store the tokens on [[= product_name_cloud =]], you must define `config/jwt` | ||
| as a volume in `.platform.app.yaml`. If you have a 3-node-cluster setup, you must ensure the key pair is the same on all | ||
| 3 servers. Either use a network share for this, or use local mount manually copy the same keu pair | ||
| to all servers |
There was a problem hiding this comment.
Suggested change
| In order to be able to store generate and store the tokens on [[= product_name_cloud =]], you must define `config/jwt` | |
| as a volume in `.platform.app.yaml`. If you have a 3-node-cluster setup, you must ensure the key pair is the same on all | |
| 3 servers. Either use a network share for this, or use local mount manually copy the same keu pair | |
| to all servers | |
| To generate and store the tokens on [[= product_name_cloud =]], define the `config/jwt` directory as a volume in the `.platform.app.yaml` file. | |
| In 3-node cluster setups, ensure that the key pair is the same on all 3 servers. | |
| You can use a network share, or use a local mount and manually copy the key pair between the servers. |
| @@ -145,3 +145,18 @@ security: | |||
| entry_point: lexik_jwt_authentication.jwt_token_authenticator | |||
| stateless: true | |||
| ``` | |||
|
|
|||
| In order for the application to be able to generate JWT tokens, a [PEM encoded keyset needs to be generated](https://symfony.com/bundles/LexikJWTAuthenticationBundle/current/index.html#generate-the-ssl-keys) using the command: | |||
There was a problem hiding this comment.
Suggested change
| In order for the application to be able to generate JWT tokens, a [PEM encoded keyset needs to be generated](https://symfony.com/bundles/LexikJWTAuthenticationBundle/current/index.html#generate-the-ssl-keys) using the command: | |
| Finish the setup by generating a [PEM encoded key pair](https://symfony.com/bundles/LexikJWTAuthenticationBundle/2.x/index.html#generate-the-ssl-keys) by using the command: |
- I'd use
key pairconsistently, imho no need to introduce "keyset" kere - Let's use the 2.x link for the 4.6 version (I will change it when upmerging)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
N/A4.6The current instructions are incomplete, ref https://symfony.com/bundles/LexikJWTAuthenticationBundle/current/index.html#generate-the-ssl-keys
Checklist