Skip to content

Commit 7f4bd29

Browse files
Update aspnetcore/security/authentication/configure-jwt-bearer-authentication.md
Co-authored-by: Rick Anderson <[email protected]>
1 parent 445a6e2 commit 7f4bd29

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

aspnetcore/security/authentication/configure-jwt-bearer-authentication.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -333,7 +333,7 @@ It is important not to create security problems in the API so that you can test
333333

334334
Swagger and Postman are great UI tools for testing APIs. For the tools to work, the API can produce an Open API document and this can be loaded into the client testing tool. A security flow to acquire a new access token can be added to the API Open API file.
335335

336-
> Note
336+
> Warning
337337
> Do not deploy insecure security test flows to production.
338338

339339
If implementing a Swagger UI for an API, you should normally not deploy the UI to production as the security must be weakened to allow this to work.

0 commit comments

Comments
 (0)