Creating users, groups and roles by using REST API should not ignore those created in the DC Business Console Administration tab

The DC REST API to retrieve the user roles registry is:
GET /v1/repository/users-roles-registry
But in fact it does not retrieve all the users / roles.
It only retrieves "the last configuration file that was uploaded".
In fact the documentation even stipulates that: "If no file has been previously uploaded, none can be retrieved."

So if a customer first setup the users / roles with the REST API, then an other members of his team add an extra group or an extra user with the BC GUI, this information will get lost by the REST API

A user updating his list of users/groups/roles with the REST API would usually do:

1. GET /v1/repository/users-roles-registry to retrieve the most recent user/roles registry in XML Format

2. Edit the xml file to add any new groups / users / roles as needed

3. POST /v1/repository/users-roles-registry to upload the new settings

So it would be better that the GET API retrieves not the latest xml file that was uploaded, but retrieves in XML format the current setting for groups / users / roles (including groups/users that were added manually in BC)

Idea priority

Medium

Post comment

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.

Shape the future of IBM!

Search existing ideas

Post your ideas

Please use the following category to raise ideas for these offerings for all environments (traditional on premises, containers, on cloud):

Specific links you will want to bookmark for future use

Creating users, groups and roles by using REST API should not ignore those created in the DC Business Console Administration tab

Please enter your email address

RELATED IDEAS

Creating users, groups and roles by using REST API should not ignore those created in the DC Business Console Administration tab