API Documentation
|
where {userId}
is the ID of a Cocoon Data user account.
PUT
- either:userId
) userId
, which is either:This API endpoint serves a number of purposes:
userId
).userId
) which is either:Note: For more information about retrieving Cocoon Data user account IDs, see <access-service>/api/v1/users and <access-service>/api/v1/organisations/{orgGroupId}/users.
This API endpoint supports requests utilizing Cocoon Data user accounts with the following roles (as described in the SafeShare Administrator's and Organisation Administrator's Guides):
{userId}
in the request's URL) is also a member of.The Cocoon Data Platform's resources available to a Cocoon Data user meeting the criteria above is determined by the access token submitted in the header of requests to this endpoint.
The appropriate access token as the Bearer
token:
Authorization: Bearer eyJhbGciOiJSUzI1NiJ9.eyJleHAiOjE0NjcwMTY2NjYsInVzZXJfbmFtZSI6ImFsZXgub...
The following header is required if the body of the request has a JSON object:
Content-Type: application/json
The following parameter must be sent in the body of the PUT request, each as individual member of a JSON object:
true
to enable 2FA on the Cocoon Data user account represented by userId
in the request's URL or false
to disable 2FA on this account. true
to reconfigure 2FA for the Cocoon Data user represented by userId
in the URL. If the request succeeded, then an HTTP response status 200 OK
is returned.