Actions
Feature #15656
open
Feature #15650: Kea Feature Integration for parity with ISC DHCP
Options to expose Kea REST API (IPv4 and IPv6)
Status:
New
Priority:
Normal
Assignee:
-
Category:
DHCP (IPv4)
Target version:
-
Start date:
Due date:
% Done:
0%
Estimated time:
Plus Target Version:
Release Notes:
Default
Description
In ISC DHCP the GUI had (effectively) a global option to enable OMAPI support. Kea doesn't have that, but it has a REST API (which we use for HA). I'm not certain how much use the OMAPI option received, but I could see more people being interested in a REST API.
Should we generalize that and split off the REST API enable/disable from HA? Or it is not worth the effort needed to support and secure the API?
If it's not viable, this can be closed.
No data to display
Actions