Table of Contents
To use the User Management Service, a User Management Profile needs to be defined.
It requires the following components:
The Profile exposes the following endpoint-kinds:
The User Management Service requires a Token Service in order to be able to authorize access, for example against an
SQL database or a SCIM backend webservice. This means that a oauth-service must be configured, then linked to from
the User Management Service, as explained in the Profile configuration documentation.
If it is desired to configure in detail the authorization policies for each endpoint and resource type, an
Authorization Manager may be configured as well.
Finally, data-sources must be configured for the User Management Service.
You may configure the following data-sources (which may point to the same data-source instance, or different ones):
When an Authorization Manager is configured to manage authorization policies on the User Management Service, the
configured oauth-service must use the same user-account-data-source as the User Management Service so that
authorization decisions may succeed. This is not currently enforced by configuration.
If you want to allow user credentials to be updated via the User Management Service, you must also configure a
This guide will walk through the mandatory settings that are needed in order to deploy the User Management service. It will illustrate the Web UI approach and then the same settings using the Command Line Interface
Start by in the main screen of the Web User Interface in the top level menu called User Management click New Profile.
The following screen is shown. (The type is pre-selected to be um:user-management.
Fig. 130 Name the new profile
This will prompt you with a dialog requiring a name for the profile. This can be anything, but the name can be used to identity the profile in web-requests as the realm parameter, so picking a meaningful name is recommended.
admin@localhost% edit profiles profile UserManagementService user-management-service settings user-management-service
[edit profiles profile UserManagementService user-management-service settings user-management-service]
This adds the base for the new profile and navigates the admin down to the configuration of the profile at the same time
The next step is to select an OAuth profile that should be used to protect the API. All requests to the API need an access token issued by the selected OAuth profile.
In the General page of the new User Management profile select an existing OAuth profile.
Fig. 131 Select OAuth profile
admin@localhost% set api-authentication oauth-service oauth-dev
The main purpose of the User Management Service is to show user profiles. This means user account information. Therefore the profile needs to be configured with an User Account Data Source. This is the data source where the primary account is stored.
Click Data Sources in the left-hand menu and then select the data source to use as primary data source in the dropdown.
Fig. 132 Selecting a User Account Data Source
admin@localhost% set user-account-data-source Win01AD
Next to the users data source dropdown, is the OAuth Delegations dropdown. Here you should select the data-source where all the tokens are stored. This is so the User Management profile can provide the token information (not the tokens themselves) that belongs to a user via the delegations endpoint. This means that and admin can revoke and view tokens issued for a specific user.
Fig. 133 Selecting Delegations Data Source
admin@localhost% set token-data-source DefaultHSQLDB
The last required step is to setup the endpoints that should be exposed. If delegations aren’t needed then that option can be omitted.
Click the Endpoints page in the left hand menu, and add two new rows. Name the endpoints appropriately, this is used when deploying them on a node.
Set a path to the each endpoint, this will be the path they are accessed by in the API.
Create one endpoint of type um-api.
Fig. 134 Adding Endpoints to the Profile
In this step we need to move up in the configuration tree a few levels since the endpoints are configured directly on the profile, and not down in the settings where we’ve been operating. Note the response from the CLI to see where in the tree the CLI is standing.
[edit profiles profile UserManagementService user-management-service settings]
[edit profiles profile UserManagementService user-management-service]
admin@localhost% set endpoints endpoint um-api1 endpoint-kind um-api uri /um/api
With the above 5 steps the profile exists and is active. But it’s not reachable before the endpoints are exposed on a service (node).
Click System in the top menu bar, followed by Deployments on the lefthand menu.
Select the node that should expose the service (repeat the steps if the endpoints should be deployed on more than one node).
Scroll down to the end of the modal that opened to the Endpoints input box. By clicking in the box, it will show the possible endpoints that can be deployed, and the new endpoints should show up as options. Add the endpoints.
Fig. 135 Exposing the new endpoints on the services.
admin@localhost% set environments environment services service TestServer1 endpoints um-api1
Now the only step left is to commit the changes, which effectively validates the config and then deploys it to the running configuration of the cluster.
To deploy, click the Changes menu on the top menu and select Commit. A dialog is shown where the user can enter a comment. This is will be kept in the revision history.
Fig. 136 Commit the changes
It is optional but recommended to add a comment in the CLI when committing.
admin@localhost% commit comment "Added new User Management Service and deployed it to node TestServer1"