In case the login process takes some time we would show a "login"
button which makes the user try to click it. There is a good chance
that aroudn that time we get logged in, so the click will log the user
out.

Avoid that by not showing anything during logging in.

Add a scope so we don't have to care about naming conflicts
and set the verison to 0.1.0 since we don't have a stable API yet.

it's unused atm

lit-html no longer allows merging them in literals.

This should make it more clear what the components are used for

vpu-auth listens to login/logout events which the button emits
and the button shows data from the auth-update event.

Same hover effect, padding and cleanup the CSS etc.

It should only span the whole width in mobile mode

This should make it work in all (LTR at least) cases.

We don't want it to make the page scroll when the display is really small

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

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

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

(open menu with ENTER key)
See issue #6

Makes it focusable and react to keyboard events

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.

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.