Skip to content

Added instructions on how to generate PEM keypair, needed by JWT authentication #2812

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Aug 5, 2025
Merged

Added instructions on how to generate PEM keypair, needed by JWT authentication #2812

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
dde274b
Added instructions on how to generate key pair for JWT authentication
vidarl Jul 4, 2025
0ac6df8
Apply suggestions from code review
vidarl Jul 31, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 14 additions & 0 deletions docs/infrastructure_and_maintenance/security/development_security.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -145,3 +145,17 @@
entry_point: lexik_jwt_authentication.jwt_token_authenticator
stateless: true
```

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:

```bash
php bin/console lexik:jwt:generate-keypair
```

The generated key pair will be stored in the `config/jwt`directory.

Check warning on line 155 in docs/infrastructure_and_maintenance/security/development_security.md

View workflow job for this annotation

GitHub Actions / vale

[vale] docs/infrastructure_and_maintenance/security/development_security.md#L155 

[Ibexa.FutureTense] Use present tense instead of future.
Raw output 
{"message": "[Ibexa.FutureTense] Use present tense instead of future.", "location": {"path": "docs/infrastructure_and_maintenance/security/development_security.md", "range": {"start": {"line": 155, "column": 24}}}, "severity": "WARNING"}

!!! note "[[= product_name_cloud =]]"

To generate and store the tokens on [[= product_name_cloud =]], define the `config/jwt` directory as a volume in the `.platform.app.yaml` file.

Check warning on line 159 in docs/infrastructure_and_maintenance/security/development_security.md

View workflow job for this annotation

GitHub Actions / vale

[vale] docs/infrastructure_and_maintenance/security/development_security.md#L159 

[Ibexa.EOLWhitespace] Remove whitespace characters from the end of the line.
Raw output 
{"message": "[Ibexa.EOLWhitespace] Remove whitespace characters from the end of the line.", "location": {"path": "docs/infrastructure_and_maintenance/security/development_security.md", "range": {"start": {"line": 159, "column": 148}}}, "severity": "WARNING"}
In 3-node cluster setups, ensure that the key pair is the same on all 3 servers.

Check warning on line 160 in docs/infrastructure_and_maintenance/security/development_security.md

View workflow job for this annotation

GitHub Actions / vale

[vale] docs/infrastructure_and_maintenance/security/development_security.md#L160 

[Ibexa.EOLWhitespace] Remove whitespace characters from the end of the line.
Raw output 
{"message": "[Ibexa.EOLWhitespace] Remove whitespace characters from the end of the line.", "location": {"path": "docs/infrastructure_and_maintenance/security/development_security.md", "range": {"start": {"line": 160, "column": 85}}}, "severity": "WARNING"}
You can use a network share, or use a local mount and manually copy the key pair between the servers.