Web API: Signout: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| (2 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
The Signout operation signs out ( | The Signout operation signs out (logs out) the user from QPR ProcessAnalyzer and ends the user session. There are no parameters, and no data is returned by the operation (http status code is 204). Note that the signout gives this response even if the session has already been expired. Also the signout operation does not initiate a possible expired license renewal in case the license has expired. | ||
HTTP request header '''Authorization''' with value '''Bearer <access token>''' needs to be in place to identify the session to be signed out. | HTTP request header '''Authorization''' with value '''Bearer <access token>''' needs to be in place to identify the session to be signed out. | ||
<pre> | <pre> | ||
Url: POST /api/signout | Url: POST qprpa/api/signout | ||
</pre> | </pre> | ||
[[Category: QPR ProcessAnalyzer]] | [[Category: QPR ProcessAnalyzer]] | ||
Latest revision as of 10:00, 16 February 2022
The Signout operation signs out (logs out) the user from QPR ProcessAnalyzer and ends the user session. There are no parameters, and no data is returned by the operation (http status code is 204). Note that the signout gives this response even if the session has already been expired. Also the signout operation does not initiate a possible expired license renewal in case the license has expired.
HTTP request header Authorization with value Bearer <access token> needs to be in place to identify the session to be signed out.
Url: POST qprpa/api/signout