Actions
Feature #15656
closed
Options to expose Kea REST API (IPv4 and IPv6)
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.
Updated by Christian McDonald about 1 year ago
- Status changed from New to Closed
- Assignee set to Christian McDonald
Now that we have our own public API in the works, we probably don’t want to expose this directly.
Closing unless a more compelling argument exists.
Updated by
Actions