We now enable it by default for everyone. The plan is to load the API
user instead and not the person as a next step. This api should work
even for users that don't have a person associated.

This removes the 'show-image' (false by default) and removes the functionality
to show a user profile image in the logout dropdown.

We've never used this actively and want to clean things up, so remove it.

So we only need to define it in one place.

See issue #46

It was only used in the demo.

They were hardcoded in more places

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.

Now that we have a separate component for keyclaok we can move those
keycloak specific settings into their own attributes.

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.

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

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

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...).

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.

No final design, just a start.

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

TODO: rollup.config.js cleanup

We keep the login state in the session storage and force a login in case the user was
logged in before.

This means a page refresh will try to restore the login state (which usually should mean
that it just flashes becasue of redirects). And new visitors get the logged out state by default.