- Mar 18, 2021
-
-
Jenkins for Software Heritage authored
Update to upstream version '0.3.4' with Debian dir eb4685e403cf3f93b285919946bef4fa0a5356b0
-
Antoine R. Dumont authored
In some application, those user fields might not be filled in. As it's not enforced by keycloak, relax such constraint. Related to T2858
- Mar 17, 2021
-
-
Antoine Lambert authored
In the dictionary decoded from an OIDC access token, the iat field store the token creation date while the auth_time field store the date the OIDC session was opened. In order to get an accurate authentication time, the date stored in the iat field must be used as it corresponds to the time an access token was refreshed and thus the latest valid authentication date.
-
- Mar 15, 2021
-
-
Jenkins for Software Heritage authored
Update to upstream version '0.3.3' with Debian dir 05cdc228389a58f326c3bda3c89138be92bf367e
-
Antoine R. Dumont authored
The auth_time is not always provided depending on the authentication flow used. The field iat is provided for example in the direct grant access flow so use it instead as fallback. Related to T2858
- Mar 12, 2021
-
-
Jenkins for Software Heritage authored
Update to upstream version '0.3.2' with Debian dir 5efc84f4f4e0bba7d991426add6f11ba7bee2c66
-
Antoine R. Dumont authored
Related to T2858
- Mar 11, 2021
-
-
Jenkins for Software Heritage authored
Update to upstream version '0.3.1' with Debian dir 21498daf3b9199e0a5051f078f1fd248b2b828f1
-
Antoine R. Dumont authored
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
- Mar 09, 2021
-
-
Antoine R. Dumont authored
Related to T3079
-
Antoine R. Dumont authored
Separate python3-swh.auth from python3-swh.auth.django to avoid pulling too much dependencies. Not all applications will require the django part. Related to T3079
-
Jenkins for Software Heritage authored
Update to upstream version '0.3.0' with Debian dir 60fc60264a50eec818fa87bdb165ec7fa83d18c3
-
Antoine R. Dumont authored
Related to T3079
-
Antoine R. Dumont authored
Related to T3079
-
Antoine R. Dumont authored
-
Antoine R. Dumont authored
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
-
- Mar 05, 2021
-
-
Jenkins for Software Heritage authored
Update to upstream version '0.2.0' with Debian dir f40d03f6488801d3ed5b091ce82679b973dcba79
-
Antoine R. Dumont authored
Related to T3079
-
Antoine R. Dumont authored
Adds back python3-swh.core. It's a default deps since we depend on the cli from the swh-py-template. (we'll add a real cli soon enough)
-
Antoine R. Dumont authored
-
Jenkins for Software Heritage authored
Update to upstream version '0.1.0' with Debian dir a570db4d676f0c094b59e569772c137d1d337be4
- Mar 04, 2021
-
-
Antoine R. Dumont authored
This is needed for the incoming deposit-keycloak integration. Related to T3079
-
This will be required for modules depending on it (swh.web, swh.web.client, swh.deposit) Related to T3079
-
Antoine R. Dumont authored
Related to T3079
-
Antoine R. Dumont authored
-
Antoine R. Dumont authored
-