IntegrityError: null value in column "email" violates not-null constraint

[uw-rvitorino]

Describe the bug IntegrityError django_keycloak.middleware in append_user_info_to_request error null value in column "email" violates not-null constraint

django_keycloak/middleware.py in append_user_info_to_request (line 39) raises this error when the user_info does not contain the email property (because the Token is not valid anymore)

To Reproduce Steps to reproduce the behavior:

1. Login with your credentials in a UI calling a Django API served by this library
2. Remain in the UI and allow your token to expire
3. Click somewhere that calls the Django API
4. See error crashing the Django project

Expected behavior The middleware should try to get the email from the user info but if it's None it should return an Unauthorised response and not try to save the user info,

Screenshots

Desktop (please complete the following information):

• OS: Not relevant
• Browser: Not relevant
• Version: Not relevant

Smartphone (please complete the following information):

• Device: Not relevant
• OS: Not relevant
• Browser: Not relevant
• Version: Not relevant

Additional context N/A

[moritz89]

Ah yes, we would probably use a raise_on_error function to check the responses of all Keycloak calls. Basically everywhere requests.request() is called

[moritz89]

Could you test if this issue still persists in the v2 branch. AFAIK, this has been solved

[moritz89]

@uw-rvitorino Have you been able to check if the bug still persists in the v2 release?

[github-actions[bot]]

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 7 days.

[github-actions[bot]]

This issue was closed because it has been stalled for 7 days with no activity.