Create role mapping under ldap config object
Each ldap config object should be have its own
mapping object.
This is to align with the redfish.
https://redfish.dmtf.org/schemas/AccountService.v1_4_0.json
As per redfish, Each config will have it's own
"RemoteRoleMapping".
Mapping object should be persisted and restores
when the phosphor-ldap-conf restarts.
TestedBy:
Unit Tested.
Creation of privilege mapping.
Persist the priv-mapping.
Restores the priv-mapping.
Signed-off-by: Ratan Gupta <ratagupt@linux.vnet.ibm.com>
Change-Id: I5ab4aeffae61f9cc57c1338f94784d0fe5607cd3
diff --git a/phosphor-ldap-config/Makefile.am b/phosphor-ldap-config/Makefile.am
index 3052b6d..d6d8454 100644
--- a/phosphor-ldap-config/Makefile.am
+++ b/phosphor-ldap-config/Makefile.am
@@ -1,15 +1,18 @@
bin_PROGRAMS = phosphor-ldap-conf
-noinst_HEADERS = \
- ldap_config.hpp \
+noinst_HEADERS = ldap_config.hpp \
ldap_config_mgr.hpp \
+ ldap_mapper_entry.hpp \
+ ldap_mapper_serialize.hpp \
utils.hpp
phosphor_ldap_conf_SOURCES = \
main.cpp \
utils.cpp \
ldap_config.cpp \
- ldap_config_mgr.cpp
+ ldap_config_mgr.cpp \
+ ldap_mapper_entry.cpp \
+ ldap_mapper_serialize.cpp
phosphor_ldap_conf_LDFLAGS = $(SDBUSPLUS_LIBS) \
$(PHOSPHOR_DBUS_INTERFACES_LIBS) \