... | ... | @@ -85,7 +85,7 @@ Kea's Control Agent (CA) exposes a REST API over HTTP. The CA is an optional fea |
|
|
|
|
|
## Authentication for REST API
|
|
|
|
|
|
Kea 1.9.0 added support for basic HTTP authentication (RFC7617) to control access for incoming REST commands over HTTP. The credentials (username, password) are stored in a local Kea configuration file on disk. The username is logged with the API command so it is possible to determine which authenticated user performed each command.
|
|
|
Kea 1.9.0 added support for basic HTTP authentication [RFC7617](https://tools.ietf.org/html/rfc7617) to control access for incoming REST commands over HTTP. The credentials (username, password) are stored in a local Kea configuration file on disk. The username is logged with the API command so it is possible to determine which authenticated user performed each command.
|
|
|
|
|
|
Kea 1.9.2 introduced a new `auth` hook point. With this new hook point it is now possible to develop an external hook library to extend the access controls, integrate with another authentication authority or add role-based access control to the Control Agent.
|
|
|
|
... | ... | |