1
- .. ischooklib :: libca_rbac .so
1
+ .. ischooklib :: libdhcp_rbac .so
2
2
.. _hooks-RBAC :
3
3
4
- ``libca_rbac .so ``: Role-Based Access Control
5
- ============================================
4
+ ``libdhcp_rbac .so ``: Role-Based Access Control
5
+ ==============================================
6
6
7
7
.. _hooks-RBAC-overview :
8
8
9
9
Role-Based Access Control (RBAC) Overview
10
10
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
11
11
12
- Before the processing of commands in received HTTP requests, :ischooklib: `libca_rbac .so `
12
+ Before the processing of commands in received HTTP requests, :ischooklib: `libdhcp_rbac .so `
13
13
takes specific parameters, e.g. the common-name part of the client
14
14
certificate subject name, to assign a role to the request.
15
15
The configuration associated with this role is used to accept or reject
@@ -33,10 +33,17 @@ Here is a summary of the steps in processing a response:
33
33
34
34
.. note ::
35
35
36
- :ischooklib: `libca_rbac .so ` is available only to ISC customers with
36
+ :ischooklib: `libdhcp_rbac .so ` is available only to ISC customers with
37
37
a paid support contract. For more information on subscription options,
38
38
please complete the form at https://www.isc.org/contact.
39
39
40
+
41
+ .. note ::
42
+
43
+ Since Kea 1.7.x the RBAC is no longer limited to teh Control Agent:
44
+ it can be used by any other server supporting HTTP/HTTPS control
45
+ sockets e.g. DHCPv4, DHCPv6 and DDNS servers.
46
+
40
47
.. _hooks-RBAC-config :
41
48
42
49
Role-Based Access Control Configuration
@@ -106,12 +113,12 @@ API Commands
106
113
107
114
All commands of the REST API are described in files in the source directory
108
115
``src/share/api ``, or in installed Kea
109
- in ``.../share/kea/api ``. :ischooklib: `libca_rbac .so ` reads these files to take the name,
116
+ in ``.../share/kea/api ``. :ischooklib: `libdhcp_rbac .so ` reads these files to take the name,
110
117
the access right (i.e. ``read `` or ``write ``), and the hook name. The access right
111
- can be modified in the file but changes are only applied after the Control Agent
112
- restarts. Removing command definitions from ``.../share/kea/api `` has
118
+ can be modified in the file but changes are only applied after the server or
119
+ agent restarts. Removing command definitions from ``.../share/kea/api `` has
113
120
consequences: if the access control list is based on ``read `` or ``write `` and
114
- the definition file is missing, the Control Agent always rejects such
121
+ the definition file is missing, the server or agent always rejects such
115
122
a command. If the access controls list is using ``commands `` to specify the
116
123
name of a command and the definition file from ``.../share/kea/api `` of this
117
124
particular command is missing, the Control Agent logs an error on startup
@@ -261,7 +268,7 @@ in the Kea source and is copied below.
261
268
// Add hooks here.
262
269
" hooks-libraries" : [
263
270
{
264
- " library" : " /opt/lib/libca_rbac .so" ,
271
+ " library" : " /opt/lib/libdhcp_rbac .so" ,
265
272
" parameters" : {
266
273
// This section configures the RBAC hook library.
267
274
// Mandatory parameters.
0 commit comments