Dockerfile would not build without errors - fixed with this PR
@BeryJu thanks for the speedy reply.
I accept your answer, makes total sense - but surely a prompt to renew the consent should be displayed as opposed to just a non-descriptive error message would be the correct behaviour?
Describe the bug I noticed that I suddenly could no longer access apps that rely on Authentik for authentication using OAuth2. Instead of redirecting to the application as expected, I just got a vague "something went wrong" message.
I found no errors in the Authentik logs in Docker, but did notice (by chance) a SQL error in my Postgresql container:
ERROR: duplicate key value violates unique constraint "authentik_stages_consent_user_id_application_id_p_e44c6458_uniq" DETAIL: Key (user_id, application_id, permissions)=(4, d6ae6665-2bb0-4418-b1c8-93e2586a5a4b, ) already exists. STATEMENT: INSERT INTO "authentik_stages_consent_userconsent" ("expires", "expiring", "user_id", "application_id", "permissions") VALUES ('2022-09-29T12:24:38.680840+00:00'::timestamptz, true, 4, 'd6ae6665-2bb0-4418-b1c8-93e2586a5a4b'::uuid, '') RETURNING "authentik_stages_consent_userconsent"."id"
To allow access to the affected applications again, I had to delete the consent entries in the user interface.
To Reproduce Steps to reproduce the behavior: Unknown, as I am unsure what caused the issue in the first place.
Expected behavior Login to flow as per usual.
Version and Deployment (please complete the following information):
Additional context N/A