Delegated administration
Delegated administration lets you give fine-grained administrative access to specific users, based on a privilege mechanism.
Delegated administration is only available to Alpha realm users. For detailed information, refer to Alpha and Bravo realms → Delegated administration. |
How privileges restrict administrative access
Privileges enable you to grant fine-grained administrative access to specific endpoints and objects. For example, you could allow help desk or support users to update the information of other user accounts, but not delete user accounts or change system configuration.
You can use privileges to delegate specific administrative capabilities to non-administrative users, without exposing the IDM admin UI to those users. If a user has been granted a privilege that lets them see a list of users and user information, for example, they can access this list directly through the End User UI.
A delegated administrator does not have access to the same REST API methods as a regular administrator. IDM does not allow REST API methods such as POST or DELETE to delegated administrators. To add or remove relationships, use the PATCH method. For examples, refer to Managed roles. |
For more information on managing privileges using REST, refer to Privileges.
Determine access privileges
IDM determines what access a user has as follows:
-
IDM checks the
onRequest
script specified inrouter.json
. By default, this script callsrouter-authz.js
. -
If access requirements are not satisfied, IDM then checks for any privileges associated with the user’s roles.
onResponse
and onFailure
scripts are supported when using privileges. onFailure
scripts are called only if both the onRequest
script and the privilege filter fail. onRequest
, onResponse
, and onFailure
scripts are not required for the privilege mechanism.
Create privileges
Privileges are assigned to internal roles. A privilege specifies the following information:
-
The service path where users with that internal role have access.
-
The methods and actions allowed on that service path.
-
The specific attributes of the objects at that service path where access is allowed.
You can use a query filter within a privilege so that the privilege applies to a subset of managed objects only.
The privileges
property is an array and can contain multiple privileges. Each privilege can contain:
- accessFlags
-
A list of attributes within a managed object that you want to give access to. Each attribute has two fields:
Field Description attribute
The name of the property you are granting access to.
readOnly
(boolean)Determines what level of access is allowed.
-
Attributes marked as
"readOnly": true
can be viewed, but not edited. -
Attributes marked as
"readOnly": false
can be both viewed and edited. -
Attributes that aren’t listed in the
accessFlags
array cannot be viewed or edited.-
Privileges aren’t automatically aware of changes to the managed object schema. If new properties are added, removed, or made mandatory, you must update any existing privileges to account for these changes. When a new property is added, it has a default permission level of
NONE
in existing privileges, including when the privilege is set to access all attributes. -
PingIDM applies policy validation when creating or updating a privilege, to ensure that all required properties are writable when the
CREATE
permission is assigned. This validation doesn’t run when schema changes are made, so you must verify that any existing privileges adhere to defined policies.
-
-
- actions
-
A list of the specific actions allowed if the
ACTION
permission has been specified.Allowed actions must be explicitly listed.
- description (optional)
-
A description of the privilege.
- filter (optional)
-
This property lets you apply a static or dynamic query filter to the privilege, which can be used to limit the scope of what the privilege allows the user to access.
Example 1. Static Filter ExampleTo allow a delegated administrator to access information only about users for the
stateProvince
of Washington, include a static filter, such as:filter : "stateProvince eq \"Washington\""
Example 2. Dynamic Filter ExampleDynamic filters insert values from the authenticated resource. To allow a delegated administrator to access information only about users in their own
stateProvince
, include a dynamic filter by wrapping the parameter in curly braces:filter : "stateProvince eq \"{{stateProvince}}\""
Users with query filter privileges can’t edit the properties specified in the filter in ways that would cause the privilege to lose access to the object. For example, if a user with either of the preceding example privileges attempted to edit another user’s
stateProvince
field to a value not matching the query filter, the request would return a403 Forbidden
error.Privilege filters are an additional layer of filter to any other query filters you create. Any output must satisfy all filters to be included.
- name
-
The name of the privilege.
- path
-
The path to the service that you want to allow members of this privilege to access. For example,
managed/realm-name_user
. - permissions
-
A list of permissions this privilege allows for the given path. The following permissions are available:
VIEW
Allows reading and querying the path, such as viewing and querying managed users.
CREATE
Allows creation at the path, such as creating new managed users.
UPDATE
Allows updating or patching existing information, such as editing managed user details.
DELETE
Allows deletion, such as deleting users from
managed/realm-name_user
.ACTION
Allows users to perform actions at the given path, such as custom scripted actions.
If you use an
ACTION
permission, there can be no filters on the privilege.
Add privileges using REST
The following example creates a new support
role with privileges that let members view, create, and update information about users, but not delete users:
curl \ --header "Authorization: Bearer <token>" \ --header "Accept-API-Version: resource=1.0" \ --header "Content-Type: application/json" \ --cacert ca-cert.pem \ --request PUT \ --data '{ "name": "support", "description": "Support Role", "privileges": [ { "name": "support", "description": "Support access to user information.", "path": "managed/realm-name_user", "permissions": [ "VIEW", "UPDATE", "CREATE" ], "actions": [], "filter": null, "accessFlags": [ { "attribute" : "userName", "readOnly" : false }, { "attribute" : "mail", "readOnly" : false }, { "attribute" : "givenName", "readOnly" : false }, { "attribute" : "sn", "readOnly" : false }, { "attribute" : "accountStatus", "readOnly" : true } ] } ] }' \ "https://<tenant-env-fqdn>/openidm/internal/role/support" { "_id": "support", "_rev": "00000000bfbac2ed", "name": "support", "description": "Support Role", "temporalConstraints": [], "condition": null, "privileges": [ { "name": "support", "description": "Support access to user information.", "path": "managed/realm-name_user", "permissions": [ "VIEW", "UPDATE", "CREATE" ], "actions": [], "filter": null, "accessFlags": [ { "attribute": "userName", "readOnly": false }, { "attribute": "mail", "readOnly": false }, { "attribute": "givenName", "readOnly": false }, { "attribute": "sn", "readOnly": false }, { "attribute": "accountStatus", "readOnly": true } ] } ] }
Policies related to privileges
When creating privileges, IDM runs policies found in policy.json
and policy.js
, including the five policies used for validating privileges:
valid-accessFlags-object
-
Verifies that
accessFlag
objects are correctly formatted. Only two fields are permitted in anaccessFlag
object:readOnly
, which must be a boolean; andattribute
, which must be a string. valid-array-items
-
Verifies that each item in an array contains the properties specified in
policy.json
, and that each of those properties satisfies any specific policies applied to it. By default, this is used to verify that each privilege containsname
,path
,accessFlags
,actions
, andpermissions
properties, and that thefilter
property is valid if included. valid-permissions
-
Verifies that the permissions set on the privilege are all valid and can be achieved with the
accessFlags
that have been set. It checks:-
CREATE
permissions must have write access to all properties required to create a new object. -
CREATE
andUPDATE
permissions must have write access to at least one property. -
ACTION
permissions must include a list of allowed actions, with at least one action included. -
If any attributes have write access, then the privilege must also have either
CREATE
orUPDATE
permission. -
All permissions listed must be valid types of permission:
VIEW
,CREATE
,UPDATE
,ACTION
, orDELETE
. Also, no permissions are repeated.
-
valid-privilege-path
-
Verifies that the
path
specified in the privilege is a valid object with a schema for IDM to reference. Only objects with a schema (such asmanaged/realm-name_user
) can have privileges applied to them. valid-query-filter
-
Verifies the query filter used to filter privileges is valid.
Get privileges on a resource
To determine which privileges a user has on a service, you can query the privilege endpoint for a given resource path or object based on the user you are currently logged in as. For example, if a user is a member of the support role mentioned in the previous example, checking the user’s privileges for the managed/realm-name_user
resource would look like this:
curl \ --header "Authorization: Bearer <token>" \ --header "Accept-API-Version: resource=1.0" \ --header "Content-Type: application/json" \ --cacert ca-cert.pem \ --request GET \ "https://<tenant-env-fqdn>/openidm/privilege/managed/realm-name_user" { "VIEW": { "allowed": true, "properties": [ "userName", "givenName", "sn", "mail", "accountStatus" ] }, "CREATE": { "allowed": true, "properties": [ "userName", "givenName", "sn", "mail" ] }, "UPDATE": { "allowed": true, "properties": [ "userName", "givenName", "sn", "mail" ] }, "DELETE": { "allowed": false }, "ACTION": { "allowed": false, "actions": [] } }
In the above example, accountStatus
is listed as a property for VIEW
, but not for CREATE
or UPDATE
, because the privilege sets this property to be read only. Since both CREATE
and UPDATE
need the ability to write to a property, setting readOnly
to false applies to both permissions. If you need more granular control, split these permissions into two privileges.
In addition to checking privileges for a resource, it is also possible to check privileges for specific objects within a resource, such as managed/realm-name_user/scarter
.
Create a delegated administrator
You can use the IDM REST API to create an internal/role
with privileges that have object, array, and relationship type attribute access. You can then use that role as a delegated administrator to perform operations on those attributes.
If you want to experiment with delegated administrators in Postman, download and import this Postman collection. |
Use the following example to create a delegated administrator:
Step 1. Create a Managed Role
To ensure a role object exists when roles are requested, you must create a managed role.
curl \ --header "Authorization: Bearer <token>" \ --header "Content-Type: application/json" \ --header "If-None-Match: *" \ --request PUT \ --data '{ "name": "testManagedRole", "description": "a managed role for test" }' \ "https://<tenant-env-fqdn>/openidm/managed/realm-name_role/testManagedRole" { "_id": "testManagedRole", "_rev": "200bc5d6-7cc1-4648-a854-3137f3d9c103-181", "name": "testManagedRole", "description": "a managed role for test" }
Step 2. Create a Manager
User
curl \ --header "Authorization: Bearer <token>" \ --header "Content-Type: application/json" \ --request POST \ --data '{ "userName": "psmith", "sn": "Smith", "givenName": "Patricia", "mail": "psmith@example.com", "telephoneNumber": "082082082", "password": "Passw0rd" }' \ "https://<tenant-env-fqdn>/openidm/managed/realm-name_user/?_action=create" { "_id": "9cae97b7-3bf3-4107-96d5-39ad153629db", "_rev": "200bc5d6-7cc1-4648-a854-3137f3d9c103-1223", "userName": "psmith", "sn": "Smith", "givenName": "Patricia", "mail": "psmith@example.com", "telephoneNumber": "082082082", "accountStatus": "active", "effectiveRoles": [], "memberOfOrgIDs": [], "effectiveAssignments": [] }
Step 3. Create Additional Users
In this step, you’ll create two users with the following attributes:
-
preferences
-
manager
-
roles
curl \ --header "Authorization: Bearer <token>" \ --header "Content-Type: application/json" \ --request POST \ --data '{ "userName": "scarter", "sn": "Carter", "givenName": "Steven", "mail": "scarter@example.com", "telephoneNumber": "082082082", "password": "Passw0rd", "preferences": { "updates": true, "marketing": false }, "manager": {"_ref": "managed/realm-name_user/9cae97b7-3bf3-4107-96d5-39ad153629db"}, "roles": [{"_ref": "managed/realm-name_role/testManagedRole"}] }' \ "https://<tenant-env-fqdn>/openidm/managed/realm-name_user/?_action=create" { "_id": "917bc052-ef39-4add-ae05-0a278e2de9c0", "_rev": "200bc5d6-7cc1-4648-a854-3137f3d9c103-1238", "userName": "scarter", "sn": "Carter", "givenName": "Steven", "mail": "scarter@example.com", "telephoneNumber": "082082082", "preferences": { "updates": true, "marketing": false }, "accountStatus": "active", "effectiveRoles": [ { "_refResourceCollection": "managed/realm-name_role", "_refResourceId": "testManagedRole", "_ref": "managed/realm-name_role/testManagedRole" } ], "memberOfOrgIDs": [], "effectiveAssignments": [] }
curl \ --header "Authorization: Bearer <token>" \ --header "Content-Type: application/json" \ --request POST \ --data '{ "userName": "jdoe", "sn": "Doe", "givenName": "John", "mail": "jdoe@example.com", "telephoneNumber": "082082082", "password": "Passw0rd", "preferences": { "updates": true, "marketing": false }, "manager": {"_ref": "managed/realm-name_user/9cae97b7-3bf3-4107-96d5-39ad153629db"}, "roles": [{"_ref": "managed/realm-name_role/testManagedRole"}] }' \ "https://<tenant-env-fqdn>/openidm/managed/realm-name_user/?_action=create" { "_id": "aca0042c-9f4c-4ad5-8cf7-aca0adeb3470", "_rev": "200bc5d6-7cc1-4648-a854-3137f3d9c103-1267", "userName": "jdoe", "sn": "Doe", "givenName": "John", "mail": "jdoe@example.com", "telephoneNumber": "082082082", "preferences": { "updates": true, "marketing": false }, "accountStatus": "active", "effectiveRoles": [ { "_refResourceCollection": "managed/realm-name_role", "_refResourceId": "testManagedRole", "_ref": "managed/realm-name_role/testManagedRole" } ], "memberOfOrgIDs": [], "effectiveAssignments": [] }
Step 4. Create Another User
You will delegate an internal/role with privileges to this user in the next step:
curl \ --header "Authorization: Bearer <token>" \ --header "Content-Type: application/json" \ --request POST \ --data '{ "userName": "bjensen", "sn": "Jensen", "givenName": "Barbara", "mail": "bjensen@example.com", "telephoneNumber": "082082082", "password": "Passw0rd" }' \ "https://<tenant-env-fqdn>/openidm/managed/realm-name_user/?_action=create" { "_id": "2d726b2a-3324-44b3-ba40-91b154d4f51e", "_rev": "200bc5d6-7cc1-4648-a854-3137f3d9c103-1291", "userName": "bjensen", "sn": "Jensen", "givenName": "Barbara", "mail": "bjensen@example.com", "telephoneNumber": "082082082", "accountStatus": "active", "effectiveRoles": [], "memberOfOrgIDs": [], "effectiveAssignments": [] }
Step 5. Create an internal/role
This role will have the following privileges:
-
A
managed/realm-name_user
privilege with accessFlags attributes that are of types: “String” , “boolean” , and “number” ; but also for:-
An object type that is not a relationship (
preferences
). -
An object type that is a relationship (
manager
). -
Array types that are relationships (
roles
,authzRoles
,reports
).
-
-
A
managed/realm-name_role
privilege for viewing details of the “roles” property of a managed user. -
An
internal/role
privilege for viewing the details of the “authzRoles” property of a managed user.
You can populate the privilege For properties that are not relationships, such as |
curl \ --header "Authorization: Bearer <token>" \ --header "Content-Type: application/json" \ --header "If-None-Match: *" \ --request PUT \ --data '{ "name": "internal_role_with_object_array_and_relationship_privileges", "description": "an internal role that has privileges for object & array types and relationships", "privileges": [ { "name": "managed_user_privilege", "path": "managed/realm-name_user", "permissions": [ "VIEW", "CREATE", "UPDATE", "DELETE" ], "actions": [], "accessFlags": [ { "attribute": "userName", "readOnly": false }, { "attribute": "password", "readOnly": false }, { "attribute": "givenName", "readOnly": false }, { "attribute": "sn", "readOnly": false }, { "attribute": "mail", "readOnly": false }, { "attribute": "description", "readOnly": false }, { "attribute": "accountStatus", "readOnly": false }, { "attribute": "telephoneNumber", "readOnly": false }, { "attribute": "postalAddress", "readOnly": false }, { "attribute": "city", "readOnly": false }, { "attribute": "postalCode", "readOnly": false }, { "attribute": "country", "readOnly": false }, { "attribute": "stateProvince", "readOnly": false }, { "attribute": "preferences", "readOnly": false }, { "attribute": "roles", "readOnly": false }, { "attribute": "manager", "readOnly": false }, { "attribute": "authzRoles", "readOnly": false }, { "attribute": "reports", "readOnly": false } ] }, { "name": "managed_role_privilege", "path": "managed/realm-name_role", "permissions": [ "VIEW" ], "actions": [], "accessFlags": [ { "attribute": "name", "readOnly": true }, { "attribute": "description", "readOnly": true } ] }, { "name": "internal_role_privilege", "path": "internal/role", "permissions": [ "VIEW" ], "actions": [], "accessFlags": [ { "attribute": "name", "readOnly": true }, { "attribute": "description", "readOnly": true }, { "attribute": "authzMembers", "readOnly": true } ] } ] }' \ "https://<tenant-env-fqdn>/openidm/internal/role/testInternalRole" { "_id": "testInternalRole", "_rev": "200bc5d6-7cc1-4648-a854-3137f3d9c103-300", "name": "internal_role_with_object_array_and_relationship_privileges", "description": "an internal role that has privileges for object & array types and relationships", "temporalConstraints": [], "condition": null, "privileges": [ { "name": "managed_user_privilege", "path": "managed/realm-name_user", "permissions": [ "VIEW", "CREATE", "UPDATE", "DELETE" ], "actions": [], "accessFlags": [ { "attribute": "userName", "readOnly": false }, { "attribute": "password", "readOnly": false }, { "attribute": "givenName", "readOnly": false }, { "attribute": "sn", "readOnly": false }, { "attribute": "mail", "readOnly": false }, { "attribute": "description", "readOnly": false }, { "attribute": "accountStatus", "readOnly": false }, { "attribute": "telephoneNumber", "readOnly": false }, { "attribute": "postalAddress", "readOnly": false }, { "attribute": "city", "readOnly": false }, { "attribute": "postalCode", "readOnly": false }, { "attribute": "country", "readOnly": false }, { "attribute": "stateProvince", "readOnly": false }, { "attribute": "preferences", "readOnly": false }, { "attribute": "roles", "readOnly": false }, { "attribute": "manager", "readOnly": false }, { "attribute": "authzRoles", "readOnly": false }, { "attribute": "reports", "readOnly": false } ] }, { "name": "managed_role_privilege", "path": "managed/realm-name_role", "permissions": [ "VIEW" ], "actions": [], "accessFlags": [ { "attribute": "name", "readOnly": true }, { "attribute": "description", "readOnly": true } ] }, { "name": "internal_role_privilege", "path": "internal/role", "permissions": [ "VIEW" ], "actions": [], "accessFlags": [ { "attribute": "name", "readOnly": true }, { "attribute": "description", "readOnly": true }, { "attribute": "authzMembers", "readOnly": true } ] } ] }
Step 6. Create the Relationship Between User and internal/role
In this step, assign the internal/role from step 5 to the user created in step 4 by creating a relationship:
curl \ --header "Authorization: Bearer <token>" \ --header "Content-Type: application/json" \ --request POST \ --data '{ "_ref": "managed/realm-name_user/2d726b2a-3324-44b3-ba40-91b154d4f51e", "_refProperties": {} }' \ "https://<tenant-env-fqdn>/openidm/internal/role/testInternalRole/authzMembers?_action=create" { "_id": "2e21f423-f934-4ed7-b6fd-9883b69d52d8", "_rev": "200bc5d6-7cc1-4648-a854-3137f3d9c103-1304", "_ref": "managed/realm-name_user/2d726b2a-3324-44b3-ba40-91b154d4f51e", "_refResourceCollection": "managed/realm-name_user", "_refResourceId": "2d726b2a-3324-44b3-ba40-91b154d4f51e", "_refProperties": { "_id": "2e21f423-f934-4ed7-b6fd-9883b69d52d8", "_rev": "200bc5d6-7cc1-4648-a854-3137f3d9c103-1304" } }
Step 7. Perform Operations as a Delegated Administrator
You can now perform operations as a delegated administrator, such as:
Query All Users
The query results display all users' properties that are allowed by the privileges:
curl \ --header "X-OpenIDM-Username: bjensen" \ --header "X-OpenIDM-Password: Passw0rd" \ --request GET \ "https://<tenant-env-fqdn>/openidm/managed/realm-name_user?_queryFilter=true&_pageSize=100&_fields=*,*_ref/*" { "result": [ { "_id": "9cae97b7-3bf3-4107-96d5-39ad153629db", "_rev": "200bc5d6-7cc1-4648-a854-3137f3d9c103-1223", "userName": "psmith", "sn": "Smith", "givenName": "Patricia", "mail": "psmith@example.com", "telephoneNumber": "082082082", "accountStatus": "active", "reports": [ { "_rev": "200bc5d6-7cc1-4648-a854-3137f3d9c103-1267", "_id": "aca0042c-9f4c-4ad5-8cf7-aca0adeb3470", "userName": "jdoe", "sn": "Doe", "givenName": "John", "mail": "jdoe@example.com", "telephoneNumber": "082082082", "preferences": { "updates": true, "marketing": false }, "accountStatus": "active", "_ref": "managed/realm-name_user/aca0042c-9f4c-4ad5-8cf7-aca0adeb3470", "_refResourceCollection": "managed/realm-name_user", "_refResourceId": "aca0042c-9f4c-4ad5-8cf7-aca0adeb3470", "_refProperties": { "_id": "e01a922b-a60d-46c2-b6bc-2b821c1580b4", "_rev": "200bc5d6-7cc1-4648-a854-3137f3d9c103-1262" } }, { "_rev": "200bc5d6-7cc1-4648-a854-3137f3d9c103-1238", "_id": "917bc052-ef39-4add-ae05-0a278e2de9c0", "userName": "scarter", "sn": "Carter", "givenName": "Steven", "mail": "scarter@example.com", "telephoneNumber": "082082082", "preferences": { "updates": true, "marketing": false }, "accountStatus": "active", "_ref": "managed/realm-name_user/917bc052-ef39-4add-ae05-0a278e2de9c0", "_refResourceCollection": "managed/realm-name_user", "_refResourceId": "917bc052-ef39-4add-ae05-0a278e2de9c0", "_refProperties": { "_id": "5bc2c633-8ae1-4ea2-adf6-8aa7ce5f8e70", "_rev": "200bc5d6-7cc1-4648-a854-3137f3d9c103-1233" } } ], "manager": null, "roles": [], "authzRoles": [] }, { "_id": "917bc052-ef39-4add-ae05-0a278e2de9c0", "_rev": "200bc5d6-7cc1-4648-a854-3137f3d9c103-1238", "userName": "scarter", "sn": "Carter", "givenName": "Steven", "mail": "scarter@example.com", "telephoneNumber": "082082082", "preferences": { "updates": true, "marketing": false }, "accountStatus": "active", "reports": [], "manager": { "_rev": "200bc5d6-7cc1-4648-a854-3137f3d9c103-1223", "_id": "9cae97b7-3bf3-4107-96d5-39ad153629db", "userName": "psmith", "sn": "Smith", "givenName": "Patricia", "mail": "psmith@example.com", "telephoneNumber": "082082082", "accountStatus": "active", "_ref": "managed/realm-name_user/9cae97b7-3bf3-4107-96d5-39ad153629db", "_refResourceCollection": "managed/realm-name_user", "_refResourceId": "9cae97b7-3bf3-4107-96d5-39ad153629db", "_refProperties": { "_id": "5bc2c633-8ae1-4ea2-adf6-8aa7ce5f8e70", "_rev": "200bc5d6-7cc1-4648-a854-3137f3d9c103-1233" } }, "roles": [ { "_rev": "200bc5d6-7cc1-4648-a854-3137f3d9c103-181", "_id": "testManagedRole", "name": "testManagedRole", "description": "a managed role for test", "_ref": "managed/realm-name_role/testManagedRole", "_refResourceCollection": "managed/realm-name_role", "_refResourceId": "testManagedRole", "_refProperties": { "_id": "a33e2de0-83ff-481c-b8a7-8ffbc02d135c", "_rev": "200bc5d6-7cc1-4648-a854-3137f3d9c103-1235" } } ], "authzRoles": [] }, { "_id": "aca0042c-9f4c-4ad5-8cf7-aca0adeb3470", "_rev": "200bc5d6-7cc1-4648-a854-3137f3d9c103-1267", "userName": "jdoe", "sn": "Doe", "givenName": "John", "mail": "jdoe@example.com", "telephoneNumber": "082082082", "preferences": { "updates": true, "marketing": false }, "accountStatus": "active", "reports": [], "manager": { "_rev": "200bc5d6-7cc1-4648-a854-3137f3d9c103-1223", "_id": "9cae97b7-3bf3-4107-96d5-39ad153629db", "userName": "psmith", "sn": "Smith", "givenName": "Patricia", "mail": "psmith@example.com", "telephoneNumber": "082082082", "accountStatus": "active", "_ref": "managed/realm-name_user/9cae97b7-3bf3-4107-96d5-39ad153629db", "_refResourceCollection": "managed/realm-name_user", "_refResourceId": "9cae97b7-3bf3-4107-96d5-39ad153629db", "_refProperties": { "_id": "e01a922b-a60d-46c2-b6bc-2b821c1580b4", "_rev": "200bc5d6-7cc1-4648-a854-3137f3d9c103-1262" } }, "roles": [ { "_rev": "200bc5d6-7cc1-4648-a854-3137f3d9c103-181", "_id": "testManagedRole", "name": "testManagedRole", "description": "a managed role for test", "_ref": "managed/realm-name_role/testManagedRole", "_refResourceCollection": "managed/realm-name_role", "_refResourceId": "testManagedRole", "_refProperties": { "_id": "1528ab24-3ec3-4113-ac3f-26cc71a2d678", "_rev": "200bc5d6-7cc1-4648-a854-3137f3d9c103-1264" } } ], "authzRoles": [] }, { "_id": "2d726b2a-3324-44b3-ba40-91b154d4f51e", "_rev": "200bc5d6-7cc1-4648-a854-3137f3d9c103-1305", "userName": "bjensen", "sn": "Jensen", "givenName": "Barbara", "mail": "bjensen@example.com", "telephoneNumber": "082082082", "accountStatus": "active", "reports": [], "manager": null, "roles": [], "authzRoles": [ { "_rev": "200bc5d6-7cc1-4648-a854-3137f3d9c103-300", "_id": "testInternalRole", "name": "internal_role_with_object_array_and_relationship_privileges", "description": "an internal role that has privileges for object & array types and relationships", "_ref": "internal/role/testInternalRole", "_refResourceCollection": "internal/role", "_refResourceId": "testInternalRole", "_refProperties": { "_id": "2e21f423-f934-4ed7-b6fd-9883b69d52d8", "_rev": "200bc5d6-7cc1-4648-a854-3137f3d9c103-1304" } } ] } ], "resultCount": 4, "pagedResultsCookie": null, "totalPagedResultsPolicy": "NONE", "totalPagedResults": -1, "remainingPagedResults": -1 }
Read a Specified User’s Preferences Object
curl \ --header "X-OpenIDM-Username: bjensen" \ --header "X-OpenIDM-Password: Passw0rd" \ --request GET \ "https://<tenant-env-fqdn>/openidm/managed/realm-name_user/aca0042c-9f4c-4ad5-8cf7-aca0adeb3470?_fields=preferences" { "_id": "aca0042c-9f4c-4ad5-8cf7-aca0adeb3470", "_rev": "200bc5d6-7cc1-4648-a854-3137f3d9c103-1267", "preferences": { "updates": true, "marketing": false } }
Query a Specified User’s Roles
curl \ --header "X-OpenIDM-Username: bjensen" \ --header "X-OpenIDM-Password: Passw0rd" \ --request GET \ "https://<tenant-env-fqdn>/openidm/managed/realm-name_user/917bc052-ef39-4add-ae05-0a278e2de9c0/roles?_queryFilter=true&_fields=*" { "result": [ { "_id": "a33e2de0-83ff-481c-b8a7-8ffbc02d135c", "_rev": "200bc5d6-7cc1-4648-a854-3137f3d9c103-1235", "name": "testManagedRole", "description": "a managed role for test", "_refResourceCollection": "managed/realm-name_role", "_refResourceId": "testManagedRole", "_refResourceRev": "200bc5d6-7cc1-4648-a854-3137f3d9c103-181", "_ref": "managed/realm-name_role/testManagedRole", "_refProperties": { "_id": "a33e2de0-83ff-481c-b8a7-8ffbc02d135c", "_rev": "200bc5d6-7cc1-4648-a854-3137f3d9c103-1235" } } ], "resultCount": 1, "pagedResultsCookie": null, "totalPagedResultsPolicy": "NONE", "totalPagedResults": -1, "remainingPagedResults": -1 }
Read a Specified User’s Manager
curl \ --header "X-OpenIDM-Username: bjensen" \ --header "X-OpenIDM-Password: Passw0rd" \ --request GET \ "https://<tenant-env-fqdn>/openidm/managed/realm-name_user/917bc052-ef39-4add-ae05-0a278e2de9c0/manager?_fields=*" { "_id": "5bc2c633-8ae1-4ea2-adf6-8aa7ce5f8e70", "_rev": "200bc5d6-7cc1-4648-a854-3137f3d9c103-1233", "userName": "psmith", "sn": "Smith", "givenName": "Patricia", "mail": "psmith@example.com", "telephoneNumber": "082082082", "accountStatus": "active", "_refResourceCollection": "managed/realm-name_user", "_refResourceId": "9cae97b7-3bf3-4107-96d5-39ad153629db", "_refResourceRev": "200bc5d6-7cc1-4648-a854-3137f3d9c103-1223", "_ref": "managed/realm-name_user/9cae97b7-3bf3-4107-96d5-39ad153629db", "_refProperties": { "_id": "5bc2c633-8ae1-4ea2-adf6-8aa7ce5f8e70", "_rev": "200bc5d6-7cc1-4648-a854-3137f3d9c103-1233" } }
Update a Specified User’s Reports
curl \ --header "X-OpenIDM-Username: bjensen" \ --header "X-OpenIDM-Password: Passw0rd" \ --header "Content-Type: application/json" \ --request PATCH \ --data '[ { "operation" : "replace", "field" : "reports", "value" : [{"_ref" : "managed/realm-name_user/917bc052-ef39-4add-ae05-0a278e2de9c0"}] } ]' \ "https://<tenant-env-fqdn>/openidm/managed/realm-name_user/9cae97b7-3bf3-4107-96d5-39ad153629db" { "_id": "9cae97b7-3bf3-4107-96d5-39ad153629db", "_rev": "200bc5d6-7cc1-4648-a854-3137f3d9c103-1223", "userName": "psmith", "sn": "Smith", "givenName": "Patricia", "mail": "psmith@example.com", "telephoneNumber": "082082082", "accountStatus": "active" }
Assign a Specified User’s Manager
curl \ --header "X-OpenIDM-Username: bjensen" \ --header "X-OpenIDM-Password: Passw0rd" \ --header "Content-Type: application/json" \ --request PATCH \ --data '[ { "operation": "add", "field": "manager", "value": {"_ref" : "managed/realm-name_user/9cae97b7-3bf3-4107-96d5-39ad153629db"} } ]' \ "https://<tenant-env-fqdn>/openidm/managed/realm-name_user/aca0042c-9f4c-4ad5-8cf7-aca0adeb3470" { "_id": "aca0042c-9f4c-4ad5-8cf7-aca0adeb3470", "_rev": "200bc5d6-7cc1-4648-a854-3137f3d9c103-1517", "userName": "jdoe", "sn": "Doe", "givenName": "John", "mail": "jdoe@example.com", "telephoneNumber": "082082082", "preferences": { "updates": true, "marketing": false }, "accountStatus": "active" }
Remove a Specified User’s Manager
curl \ --header "X-OpenIDM-Username: bjensen" \ --header "X-OpenIDM-Password: Passw0rd" \ --header "Content-Type: application/json" \ --request PATCH \ --data '[ { "operation": "remove", "field": "manager" } ]' \ "https://<tenant-env-fqdn>/openidm/managed/realm-name_user/aca0042c-9f4c-4ad5-8cf7-aca0adeb3470" { "_id": "aca0042c-9f4c-4ad5-8cf7-aca0adeb3470", "_rev": "200bc5d6-7cc1-4648-a854-3137f3d9c103-1545", "userName": "jdoe", "sn": "Doe", "givenName": "John", "mail": "jdoe@example.com", "telephoneNumber": "082082082", "preferences": { "updates": true, "marketing": false }, "accountStatus": "active" }
Update a Specified User’s Manager
curl \ --header "X-OpenIDM-Username: bjensen" \ --header "X-OpenIDM-Password: Passw0rd" \ --header "Content-Type: application/json" \ --request PATCH \ --data '[ { "operation": "replace", "field": "manager", "value": {"_ref" : "managed/realm-name_user/aca0042c-9f4c-4ad5-8cf7-aca0adeb3470"} } ]' \ "https://<tenant-env-fqdn>/openidm/managed/realm-name_user/917bc052-ef39-4add-ae05-0a278e2de9c0" { "_id": "917bc052-ef39-4add-ae05-0a278e2de9c0", "_rev": "200bc5d6-7cc1-4648-a854-3137f3d9c103-1565", "userName": "scarter", "sn": "Carter", "givenName": "Steven", "mail": "scarter@example.com", "telephoneNumber": "082082082", "preferences": { "updates": true, "marketing": false }, "accountStatus": "active" }
Delete a Specified User
curl \ --header "X-OpenIDM-Username: bjensen" \ --header "X-OpenIDM-Password: Passw0rd" \ --header "Content-Type: application/json" \ --request DELETE \ "https://<tenant-env-fqdn>/openidm/managed/realm-name_user/9cae97b7-3bf3-4107-96d5-39ad153629db" { "_id": "9cae97b7-3bf3-4107-96d5-39ad153629db", "_rev": "200bc5d6-7cc1-4648-a854-3137f3d9c103-1223", "userName": "psmith", "sn": "Smith", "givenName": "Patricia", "mail": "psmith@example.com", "telephoneNumber": "082082082", "accountStatus": "active" }
Create a User
-
Using POST:
curl \ --header "Content-Type: application/json" \ --header "X-OpenIDM-Username: bjensen" \ --header "X-OpenIDM-Password: Passw0rd" \ --request POST \ --data '{ "userName": "psmith", "sn": "Smith", "givenName": "Patricia", "mail": "psmith@example.com", "telephoneNumber": "082082082", "password": "Passw0rd" }' \ "https://<tenant-env-fqdn>/openidm/managed/realm-name_user" { "_id": "1a20930b-cf61-4b43-a730-9f73af9147cb", "_rev": "200bc5d6-7cc1-4648-a854-3137f3d9c103-571", "userName": "psmith", "sn": "Smith", "givenName": "Patricia", "mail": "psmith@example.com", "telephoneNumber": "082082082", "accountStatus": "active" }
-
Using PUT:
curl \ --header "Content-Type: application/json" \ --header "X-OpenIDM-Username: bjensen" \ --header "X-OpenIDM-Password: Passw0rd" \ --header "If-None-Match: *" \ --request PUT \ --data '{ "userName": "psmith", "sn": "Smith", "givenName": "Patricia", "mail": "psmith@example.com", "telephoneNumber": "082082082", "password": "Passw0rd" }' \ "https://<tenant-env-fqdn>/openidm/managed/realm-name_user/psmith" { "_id": "psmith", "_rev": "200bc5d6-7cc1-4648-a854-3137f3d9c103-590", "userName": "psmith", "sn": "Smith", "givenName": "Patricia", "mail": "psmith@example.com", "telephoneNumber": "082082082", "accountStatus": "active" }
Delegated administration may not work as expected if |
For more examples, including working with filters, refer to the Postman collection. |
All patches are done with a PATCH request. Delegated administrator operations do not currently support using POST actions for patch requests (POST |