REST Resources
-
/ -
/active-user-sessions -
/active-user-sessions /{id} -
/api-access-profiles -
/api-access-profiles /{id} -
/capabilities -
/capabilities /{cid} /roles /{rid} -
/capabilities /{cid} /tasks /{tid} -
/capabilities /{id} -
/capabilities /{id} /roles -
/capabilities /{id} /tasks -
/certificate -
/certificate /{certificate-id} -
/check-enabled-tasks -
/clear-local-passwords -
/disable-users -
/enable-users -
/generate-temp-password -
/job-instances /{job-id} /export-roles-data -
/job-instances /{job-id} /terminate-user-session-job-results -
/login -
/login-status -
/logout -
/profiles -
/profiles /{id} -
/profiles /{id} /roles -
/profiles /{id} /roles /{rid} -
/roles -
/roles /{id} -
/roles /{role-id} /capabilities -
/roles /{role-id} /capabilities /{capability-id} -
/roles /{role-id} /tasks -
/roles /{role-id} /tasks /{task-id} -
/tasks -
/tasks /{id} -
/terminate-user-sessions -
/unlock-users -
/upload-image -
/user-preference-states -
/user-profiles -
/user-profiles /{profile-id} -
/users -
/users /{id} -
/users /{id} /active-user-sessions -
/users /{id} /disable-user -
/users /{id} /enable-user -
/users /{id} /roles -
/users /{uid} /active-user-sessions /{rid} -
/users /{uid} /roles /{rid} -
/users /{user-id} /capabilities -
/users /{user-id} /change-password -
/users /{user-id} /image -
/users /{user-id} /validate-password -
/validate-password
/api/space/user-management/logout
The following operation is supported on this resource:
- POST - Logout from Space by terminating current client's REST API Session
| POST /logout | Version 1 |
This API terminates the user session created by the /api/space/user-management/login API. After the user is logged out, subsequent HTTP session requests to the server will not be granted access, unless, the client provides proper credentials or an X.509 certificate in the request header.
Both the JSESSIONID and JSESSIONIDSSO headers must be passed to the API, in order for the API to locate the user session. This is automatically done by most HTTP Clients.
If the logout is successful, a 200 (Success) Error Code will be returned by the API, along with the response body of:
User logged out
If the logout is unsuccessful then, one of these Error Codes will be returned:
- 401 (Unauthorized) - Incorrect headers were passed in to the API.
- 412 (Precondition Failed) - Correct headers were passed in, but logout was still unsuccessful.
Sample Usage
POST /logout
- Accept Headers:
application/vnd.net.juniper.space.user-management.user-ref+xml;version=1
application/vnd.net.juniper.space.user-management.user-ref+json;version=1
Access Control
The following capabilities are required to access this API: DefaultRead