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 1 commit
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
15 changes: 15 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,18 @@
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:

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

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

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 =]]"

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
Loading