Skip to content

Commit ec1e833

Browse files
committed
Use Curl
1 parent 7f4bd29 commit ec1e833

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -329,9 +329,9 @@ Testing secure APIs can be implemented in different ways. Integration tests and
329329

330330
It is important not to create security problems in the API so that you can test the API. When delegated access tokens are used, it is more difficult to test as the tokens can only be created using a UI and an OpenID Connect flow. If using a test tool to create the delegated access tokens, security features must be disabled for the tests. It is important that the features are only disabled in the test environment.
331331

332-
### Use Swagger, Postman and other API UI tools
332+
### Use Swagger, Curl and other API UI tools
333333

334-
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.
334+
Swagger and Curl 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

336336
> Warning
337337
> Do not deploy insecure security test flows to production.

0 commit comments

Comments
 (0)