Skip to content

Commit 4c68edc

Browse files
authored
doc(jwt): fix broken links
1 parent 37a7080 commit 4c68edc

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

core/jwt.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -42,7 +42,7 @@ The keys should not be checked in to the repository (i.e. it's in `api/.gitignor
4242
only pass signature validation against the same pair of keys it was signed with. This is especially relevant in a production
4343
environment, where you don't want to accidentally invalidate all your clients' tokens at every deployment.
4444

45-
For more information, refer to [the bundle's documentation](https://github.com/lexik/LexikJWTAuthenticationBundle/blob/master/Resources/doc/index.md)
45+
For more information, refer to [the bundle's documentation](https://github.com/lexik/LexikJWTAuthenticationBundle/blob/master/Resources/doc/index.rst)
4646
or read a [general introduction to JWT here](https://jwt.io/introduction/).
4747

4848
We're not done yet! Let's move on to configuring the Symfony SecurityBundle for JWT authentication.
@@ -105,7 +105,7 @@ authentication_token:
105105
```
106106

107107
If you want to avoid loading the `User` entity from database each time a JWT token needs to be authenticated, you may consider using
108-
the [database-less user provider](https://github.com/lexik/LexikJWTAuthenticationBundle/blob/master/Resources/doc/8-jwt-user-provider.md) provided by LexikJWTAuthenticationBundle. However, it means you will have to fetch the `User` entity from the database yourself as needed (probably through the Doctrine EntityManager).
108+
the [database-less user provider](https://github.com/lexik/LexikJWTAuthenticationBundle/blob/master/Resources/doc/8-jwt-user-provider.rst) provided by LexikJWTAuthenticationBundle. However, it means you will have to fetch the `User` entity from the database yourself as needed (probably through the Doctrine EntityManager).
109109

110110
Refer to the section on [Security](security.md) to learn how to control access to API resources and operations. You may
111111
also want to [configure Swagger UI for JWT authentication](#documenting-the-authentication-mechanism-with-swaggeropen-api).
@@ -189,8 +189,8 @@ The "Authorize" button will automatically appear in Swagger UI.
189189
### Adding a New API Key
190190

191191
All you have to do is configure the API key in the `value` field.
192-
By default, [only the authorization header mode is enabled](https://github.com/lexik/LexikJWTAuthenticationBundle/blob/master/Resources/doc/index.md#2-use-the-token) in LexikJWTAuthenticationBundle.
193-
You must set the [JWT token](https://github.com/lexik/LexikJWTAuthenticationBundle/blob/master/Resources/doc/index.md#1-obtain-the-token) as below and click on the "Authorize" button.
192+
By default, [only the authorization header mode is enabled](https://github.com/lexik/LexikJWTAuthenticationBundle/blob/master/Resources/doc/index.rst#2-use-the-token) in LexikJWTAuthenticationBundle.
193+
You must set the [JWT token](https://github.com/lexik/LexikJWTAuthenticationBundle/blob/master/Resources/doc/index.rst#1-obtain-the-token) as below and click on the "Authorize" button.
194194

195195
`Bearer MY_NEW_TOKEN`
196196

0 commit comments

Comments
 (0)