- URL:
- https://<root>/security/users/refreshMembership
- Methods:
POST- Version Introduced:
- 10.3
Access requirements
Required privileges
The Portal Administrator API requires privilege-based access. An administrator must be assigned a specific user privilege, or role, to access any given endpoint. Listed below are the user privileges or roles an administrator can be assigned that provides access to this endpoint. If multiple privileges are listed, only one needs to be assigned to gain access.
Tokens
This API requires token-based authentication. A token is automatically generated for administrators who sign in to the Portal Administrator API directory's HTML interface. Tokens generated in this way are stored for the entirety of the session.
Those accessing the API directory outside of the HTML interface will need to acquire a session token from the generate operation in the Portal Directory API. For security reasons, all POST requests made to the Portal Administrator API must include a token in the request body.
Description
The refresh operation iterates over every enterprise group configured in an organization and determines if the user accounts listed in the users parameter belong to any of the configured enterprise groups. If there is any change in membership (a user has been added or removed from the enterprise group), the database and the indexes are updated for each user account. While ArcGIS Enterprise automatically refreshes the memberships when a user logs in and during a periodic refresh (configured through the Update Identity Store operation), this operation allows an administrator to force a refresh.
Request parameters
| Parameter | Details |
|---|---|
| The comma separated list of user names for whom the memberships need to be refreshed. Example |
| The response format. The default response format is Values: |
Example usage
The following is a sample POST request for the refresh operation:
POST /<context>/portaladmin/security/users/refreshMembership HTTP/1.1
Host: organization.example.com
Content-Type: application/x-www-form-urlencoded
Content-Length: []
users=jdoe@domain,aturing@domain&f=jsonJSON Response example
{"status": "success"}