Obtains a bearer access token that can be used to authenticate the subject making this request during
future requests. All bearer access tokens for this subject that have been obtained earlier are invalidated
by this request. The subject can be authenticated by means of
a session ID given as the value for the JSESSIONID cookie. Alternatively, the subject can be authenticated using
password POST parameters. Subject authentication may also
work by providing a bearer access token as obtained by an earlier call to this
service end point. The bearer token has to be provided as an HTTP request header field "Authorization: Bearer <bearer-token>"
Lastly, basic authentication can be used where technically the username and password are provided as base64-encoded string in
the "Authorization:" header field like this: "Authorization: Basic QWxhZGRpbjpvcGVuIHNlc2FtZQ==". Most REST clients use
shorthand URL notations with ":" and "@" to denote basic authentication, with these URL elements not being logged.
|Output format:||JSON document of the following format
Using the session ID in a session cookie:
Using POST username and password form parameters:
Using a bearer access token:
Using basic authentication: