Skip to content
This repository has been archived by the owner on Nov 13, 2021. It is now read-only.

Latest commit

 

History

History
22 lines (15 loc) · 1.15 KB

File metadata and controls

22 lines (15 loc) · 1.15 KB

Practical API Guidelines - Should have

  1. Validating OpenAPI Specifications
  2. APISecurity

Validating OpenAPI Specifications

Writing OpenAPI specs is easy, writing good OpenAPI specs is a different story.

Maturity level one covered how you can document & generate OpenAPI specifications, however that is only the start.

You should:

  • Add your OpenAPI specs to source control given this is part of your application
  • Validate changes to your OpenAPI specs to avoid specification violations (user guide)
  • Unit test Open API validation to automatically detect breaking changes

API Security

API security is an essential part when designing the API. All different levels of security are discussed within the API-Security document (user guide).

You should:

  • When possible, use a token based authenticaton/authorization (OAuth2, MSI, etc..)
  • When not, depending on the use case, consider to use a combination of the available security mechanisms (e.g. Client Certificate, api key, ip filtering, etc..)