Define the Schema
Managed objects and their properties are defined in the
conf/managed.json file. The schema in this file is not a comprehensive list of all the properties that can be stored in the IDM repository. If you use a generic object mapping, you can create a managed object with any arbitrary property, and that property will be stored in the repository. However, if you create an object with properties that are not defined in
conf/managed.json, those properties are not visible in the UI. In addition, you won't be able to configure the "sub-properties" that are described in the following section.
For explicit object mappings, the schema must be mapped to tables and columns in the JDBC database or to organizational units in DS. For more information about explicit and generic object mappings, see "Generic and Explicit Object Mappings".
The Admin UI depends on the presence of specific core schema elements, such as users, roles, and assignments (and the default properties nested within them). If you remove such schema elements, and you use the Admin UI to configure IDM, you must modify the Admin UI code accordingly. For example, if you remove the entire
assignment object from
conf/managed.json, the UI will throw exceptions wherever it queries this schema element.