The authentication credentials for the User (that is, the currently logged-in user.)

This includes:

• The cred's Username
• The cred's authentication token

By design, there is no way to access the token directly as a String. It can be added to a header to a HttpBuilder for a request, or encoded into local storage, but that's it.

This token should never be rendered to the end user, and with this API, it can't be!

Return the username stored into the credentials.

For convenience, to avoid having to import Api.Endpoint when using Api.

A register request that will decode the credentials into the Cred opaque type.

A login request that will decode the credentials into the Cred opaque type.

HTTP GET request.

HTTP POST request.

HTTP PUT request.

HTTP DELETE request.

It does not require any body as the url is enough to identify the targeted resource.

A user update request that will decode the credentials into the Cred opaque type.

A custom application that knows how to decode the potential credentials from the flags.

Store the given session fields together with the credentials into local storage.

An event listener for session changes. It will trigger for any change of the session stored into the local storage, even those from other browser tabs or windows.