In certain versions of Analyze, double clicking a user in the user list may cause the user preferences to disappear. This will prevent the users from logging in until the preferences are recreated.
This issue is slated to be corrected in v3.4.4 and v3.5.1, but if you encounter it prior to upgrading, the instructions below will recreate the user permissions:
- Get a login token. In the browser, hit F12 to load the browser console and go to the Network tab. Back in the application, do something that triggers an API request to appear in the browser console. Go to that request and you should see in the request header an ltk key, take the value - this is your login token for use further down.
- Go to <analyze-url>/api-viewer
- Under "users" section expand "GET /api/v3/users", fill in the following, then hit "Try it out!":
- ltk: the token from #1
- container: object:!tenant:defaultTenant
- Find your bad user in the list, it will have the following parameters set:
"active": false,
"state": null, - Take a copy of the full user, which will look like:
{
"id": "15d557c3-5b10-47cd-b371-9948e630e99c",
"tenant": "defaultTenant",
"name": "userOne",
"imported": false,
"active": false,
"state": null,
"principalImportDetails": null
} - Take a copy of the user's locator, which will look like:
"locator": "object:!tenant:defaultTenant~user:15d557c3-5b10-47cd-b371-9948e630e99c"
- Under "users" section expand "PUT /api/v3/users/{locator}", fill in the following, then hit "Try it out!":
- ltk: the token from #1
- locator: the value from #4
- body: the full details from #4, but change the following two parameters:
"active": true,
A sample of the full body should look like this (if it is an imported user than there will be more information under "principalImportDetails"):
"state": "ACTIVE",
{
"id": "15d557c3-5b10-47cd-b371-9948e630e99c",
"tenant": "defaultTenant",
"name": "userOne",
"imported": false,
"active": true,
"state": "ACTIVE",
"principalImportDetails": null
}
- On success, the user preferences are successfully reinstated and the user will be able to login again.
Comments
0 comments
Please sign in to leave a comment.