By setting a max-width on the element it will use ellipsis to shorten the
user name

This reverts commit 1416d0ac942c8bf6f6d52efc03f9f59e6087b2fe.

Neuber, Eugen Ramon authored 4 years ago and Reiter, Christoph committed 4 years ago

See issue #9

If the page prevents the default handler in beforeunload the logout
never occurs and we end up in an endless transient "logging-out" state.

Prevent this by reverting the login status back in that case.

We don't want to depend on harcoded values in the build

In some cases we want to set the path via a html attribute where we can't easily
compute a URL relative to the bundle or page. Convert a path to an URL
if parsing it as an URL doesn't work instead.

No longer needed

These scopes get used for the keycloak login and in case they are registered
as optional scopes for that client get added to the access token.

See #7

This makes it easier to test actual requests and to debug the token content

With keycloak 9.0 the kcLocale option is gone and the locale selection has been reworked.
If I understand things correctly using the "locale" option should start working with 9.0,
so pass both for now.

See https://www.keycloak.org/docs/latest/server_admin/#_user_locale_selection

Fixes #8

See https://gitlab.tugraz.at/VPU/Apps/Library/issues/41

Not sure if this helps, but worth a try.

Neuber, Eugen Ramon authored 5 years ago and Reiter, Christoph committed 4 years ago

(open menu with ENTER key)
See issue #6

See https://tools.ietf.org/html/rfc7636
Supported in Keycloak since 7.0

Makes it focusable and react to keyboard events

We always need it to check if th user is logged in already, so doing
a dynamic import doesn't give us anything and just slows things down.

We need to override everything on the prod server, and having everything in one object
makes it clear what is keycloak specific (we could also prefix everything...).

So we can use the update event to wait for the global variables in other components.

Also don't log the status when we get a request as with mulitple users we spam the logs.
Moved to the app receiving the events instead.

In case the login happens through a login iframe and the iframe src either doesn't
exist or it doesn't respond with a message then keycloak will block in init() forever.

Add a timeout so that after 5 seconds we abort the init and emit a changed event.

We use it bundled in the API docs and need to set the right server depending on the api build env.

Neuber, Eugen Ramon authored 5 years ago and Reiter, Christoph committed 4 years ago

See issue #3

This can happen when the session expires, for example if the user has logged
out in another window.

This is useful whenn you want to use "logging-out" to clear user related data.

Every change to person etc should also mean a new token, so we can reduce
duplicated events by checking if the token has changed.

For example in case the token gets refreshed we want to advertise this to all clients.

We don't need it in all cases.

With the new ability to log in without redirecting to keycloak and reloading the page
we can now try to login on start every time.

Instead of remembering the login state in the session storage we just ask keycloak in an iframe
on start. To better describe this new behaviour rename the attribute from remember-login to try-login.

The newest keycloak library supporst a mode for doing the redirect in an iframe
with a separate page that needs to be whitelisted in keycloak.

The newer version also finally fixes the native promise bugs so we might as well
use the one from npm instead of fetching it from the keycloak server at runtime.