All communication with the Chef Server must be authenticated using the Chef Server API, which is a REST API that allows requests to made to the Chef Server. Only authenticated requests will be authorized. Most of the time, and especially when using Knife, the chef-client, or the Chef Server web interface, the use of the Chef Server API is transparent. In some cases, the use of the Chef Server API requires more detail, such as when making the request in Ruby code, with a Knife plugin, or when using cURL.
| Section | Description |
|---|---|
| Authentication | The authentication process ensures that requests to the Chef Server are made only by authorized users. |
| Authorization | Users of the Chef Server can only perform authorized actions. |
| Headers and Endpoints | The Chef Server API includes endpoints for all of the objects on the Chef Server. |