You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: core/jwt.md
+4-4Lines changed: 4 additions & 4 deletions
Original file line number
Diff line number
Diff line change
@@ -42,7 +42,7 @@ The keys should not be checked in to the repository (i.e. it's in `api/.gitignor
42
42
only pass signature validation against the same pair of keys it was signed with. This is especially relevant in a production
43
43
environment, where you don't want to accidentally invalidate all your clients' tokens at every deployment.
44
44
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)
46
46
or read a [general introduction to JWT here](https://jwt.io/introduction/).
47
47
48
48
We're not done yet! Let's move on to configuring the Symfony SecurityBundle for JWT authentication.
@@ -105,7 +105,7 @@ authentication_token:
105
105
```
106
106
107
107
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).
109
109
110
110
Refer to the section on [Security](security.md) to learn how to control access to API resources and operations. You may
111
111
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.
189
189
### Adding a New API Key
190
190
191
191
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.
0 commit comments