Basic access control Stork user -> Kea access
The Kea administrator would like to be able to control who can access Kea. This includes individual Stork users, as Stork is just one channel for accessing Kea.
At the moment Stork is read-only, but it won't always be, and even controlling read-only access is important.
So it would be desirable if Stork would forward the userID of the authenticated Stork user to the Stork agent, and for this userID to be used to control the user's access to Kea, based on the privileges assigned to that user in Kea.
It is also as important as controlling access to log that access, with a time/date stamp, and what commands/api calls were executed. When there is write access (in the future) via Stork to make configuration changes, it will be particularly critical to identify who changed the configuration at what time.