Some Operations Manager components, like Cloud Controller, only use GUIDs for user identification. You can use UAA to retrieve the emails of your Operations Manager instance users either as a list or, for a specific user, with that user’s GUID.
Target your UAA server by running:
uaac target uaa.UAA-DOMAIN
Where UAA-DOMAIN
is the domain of your UAA server.
Record the uaa:admin:client_secret
from your deployment manifest.
Authenticate and obtain an access token for the admin client from the UAA server by running:
uaac token client get admin -s ADMIN-CLIENT-SECRET
Where ADMIN-CLIENT-SECRET
is the admin secret you recorded in the previous step.
UAAC stores the token in ~/.uaac.yml
.
Display the users and apps authorized by the UAA server, as well as the permissions granted to each user and app, by running:
uaac contexts
In the output from uaac contexts
, check the scope
section of the client_id: admin
user for scim.write
. The value scim.write
represents sufficient permissions to query the UAA server for user information.
If the admin user lacks permissions to change passwords, add the permissions:
Add the necessary permissions to the admin user account on the UAA server by running:
uaac client update admin --authorities "EXISTING-PERMISSIONS scim.write"
Where EXISTING-PERMISSIONS
is the current contents of the scope
section from the output from uaac contexts
.
Delete the local token by running:
uaac token delete
Obtain an updated access token from the UAA server by running:
uaac token client get admin
To list your Operations Manager instance users, run:
uaac users
By default, the uaac users
command returns information about each user account, including GUID, name, permission groups, activity status, and metadata. To limit the output of uaac users
to email addresses, run:
uaac users --attributes emails
To retrieve a specific user’s email address, run:
uaac users "id eq GUID" --attributes emails
Where GUID
is the GUID of a specific user.