Define managed object schema
Managed objects and their properties are defined in the default IDM managed object schema.
The default schema includes these types of managed objects:
| The default schema also includes application type managed objects. However, you should not alter these in any way as they are reserved for modification by Ping Identity to support workforce use cases. You should not add custom attributes to them, repurpose their default attributes, or reconcile data into them. |
Each managed object type contains properties for storing information about objects of that type. For example, the user object type has properties for storing usernames, passwords, email addresses, and so forth.
You can extend the default IDM managed object schema to meet your needs:
-
Add new managed object types. For more information, refer to Create and modify object types.
-
Specify default values for object properties. For more information, refer to Default Values.
-
Derive object property values from other object property values, known as virtual properties. For more information, refer to Calculate properties based off other properties.
-
Define custom relationships between managed objects. For more information, refer to Manage custom relationship properties.
To store custom data for users, you can add custom attributes (non-searchable) or adapt one of the general purpose extension attributes (searchable). Refer to Customize user identities.
|
Ping Identity recommends that you do not delete the default managed objects in your tenant. In many cases it can break your tenant. The IDM admin UI depends on the presence of the default managed object types and the
default properties nested within them. If you remove any of these schema elements,
and you use the IDM admin UI to configure IDM, you must modify the IDM admin UI
code accordingly. For example, if you remove the |
To interact with a managed object schema via REST, refer to Schema.