Re: [Kea-users] migrating an existing LDAP configuration

2024-04-13 Thread Darren Ankney
That is mostly accurate. Stork manages Kea via the API, so without the hooks that provide such, Stork won't be able to manage the system either. Thank you, Darren Ankney On Fri, Apr 12, 2024 at 10:53 AM Dan Geist wrote: > > The way I read (the admittedly slightly confusing set of pages) is

Re: [Kea-users] migrating an existing LDAP configuration

2024-04-12 Thread Dan Geist
The way I read (the admittedly slightly confusing set of pages) is that both MySQL and PostgreSQL are supported as configuration backends in the latest stable open source version, but the hooks to do certain things (like per-host lease reservations, bulk-lease-query and API-based configuration

Re: [Kea-users] migrating an existing LDAP configuration

2024-04-12 Thread Darren Ankney
I clicked "send" too soon. I meant to share this knowledge base article that is slightly relevant. The focus is on using Kea with pgpool-ii but it does show an example of storing the configuration in the database and working with it via the API at the end:

Re: [Kea-users] migrating an existing LDAP configuration

2024-04-12 Thread Darren Ankney
Hi Udo, That is correct. To store the configuration in the database, you would need the Configuration Backend Commands hook: https://kea.readthedocs.io/en/kea-2.4.1/arm/hooks.html#libdhcp-cb-cmds-so-configuration-backend-commands which does require a support subscription. Thank you, Darren