Set the transaction state of a CAS session
post/servers/{serverName}/sessions/{sessionId}
Sets the state of the session's transaction (valid values are start, commit, or cancel). Typical workflow would be to use this endpoint to start a transaction on the session. Next, use casAccessManagement lock transactions to lock the necessary objects. Then, modify permissions on those objects. Finally, commit or cancel the changes using this endpoint again.
| Name | Type | Required | Description |
|---|---|---|---|
serverName | string | true | The ID of the CAS server the user wishes to check the session state on. |
sessionId | string | true | The session ID of the CAS session that is being checked. |
| Status | Meaning | Description | ||
|---|---|---|---|---|
| 200 | OK | The requested session's transaction state was returned. Valid values include started or none. | ||
| 400 | Bad Request | The request was invalid. | Schema | |
| 404 | Not Found | The requested CAS server does not exist. | ||
| 409 | Conflict | The request could not be completed due to a conflict with the current state of the resource. Details are included in the response body. | ||
| 500 | Internal Server Error | The request could not be fulfilled because of an unexpected server error. |