Tester will want to craft carefully the keycloak mock so it returns
consistent data.

Currently the decoded_token and user_info are hard-coded to consistent values. So using
the default keycloak mock is ok. As soon as other testers will want another user_info,
the decoded token will diverge and not return the correct user_info subpart of the
decoded token.

This commits fixes such behavior and allows the decoded token to stay consistent with
the user_info.

Related to T2858

Related to T3079

Related to T3079

That class is a custom User proxy model for remote users storing OpenID Connect related
data (profile containing authentication tokens, ...).

The model is also not saved to database as all users are already stored in the Keycloak
one.

That class will be used for example by both the webapp and the deposit.

Related to T3079

Related to T3079

This is needed for the incoming deposit-keycloak integration.

Related to T3079

Antoine R. Dumont authored 4 years ago and Antoine R. Dumont committed 4 years ago

This will be required for modules depending on it (swh.web, swh.web.client, swh.deposit)

Related to T3079

This reworks the tests logic as well to reuse the way web tests are written.

This is a first step to actually use the mock class defined here as fixture for future
modules which will depend on swh-auth (swh-web-client, swh-web and swh-deposit).

Related to T3079

Related to T3079

Related to T3079

This reworks data sample into a dedicated module sample_date for readability.

Related to T3079

Related to T3079

Related to T3079

Related to T3079

Related to T3079