Drop-OSS/drop
1
0
Fork 0
mirror of https://github.com/Drop-OSS/drop.git synced 2026-07-25 04:15:36 -04:00
Code Issues 77 Packages Projects Releases 10 Wiki Activity

[GH-ISSUE #161] [Bug?] User profile page not found with OIDC #76

New Issue
Closed
opened 2026-02-17 17:06:03 -05:00 by yindo · 2 comments
yindo commented 2026-02-17 17:06:03 -05:00
Owner
Copy Link
Copy Source

Originally created by @tomorrow-nf on GitHub (Aug 1, 2025).
Original GitHub issue: https://github.com/Drop-OSS/drop/issues/161

  • Set up a new Drop instance with OIDC configured and password auth disabled (using Authentik in this example)

OIDC_ADMIN_GROUP=admin
DISABLE_SIMPLE_AUTH=true
OIDC_AUTHORIZATION=https://authentik.domain.tld/application/o/authorize/
OIDC_TOKEN=https://authentik.domain.tld/application/o/token/
OIDC_USERINFO=https://authentik.domain.tld/application/o/userinfo/
OIDC_SCOPES: openid,email,profile

  • Log in with a user in the designated admin role. User should be able to log in successfully.
  • Click the username in the top right, then the username again in the dropdown

Result: 404 page:
"404
Oh no!

Page not found: /user/a168770b-d50e-4b43-b0f2-456c8f58c5fa

An error occurred while responding to your request. If you believe this to be a bug, please report it. Try signing in and see if it resolves the issue."

  • No log errors
  • Non-admin users (in groups allowed through via the Authentik provider policy) see this error as well. Seems that it doesn't create a user directory appropriately for users created with OIDC
  • Also noticed that under Username -> Account Settings, the "Home", "Security", and "Settings" menus are completely blank. Not sure if this is expected or not with the early state of this tool, but may be related if not expected.
Originally created by @tomorrow-nf on GitHub (Aug 1, 2025). Original GitHub issue: https://github.com/Drop-OSS/drop/issues/161 - Set up a new Drop instance with OIDC configured and password auth disabled (using Authentik in this example) > OIDC_ADMIN_GROUP=admin > DISABLE_SIMPLE_AUTH=true > OIDC_AUTHORIZATION=https://authentik.domain.tld/application/o/authorize/ > OIDC_TOKEN=https://authentik.domain.tld/application/o/token/ > OIDC_USERINFO=https://authentik.domain.tld/application/o/userinfo/ > OIDC_SCOPES: openid,email,profile - Log in with a user in the designated admin role. User should be able to log in successfully. - Click the username in the top right, then the username again in the dropdown Result: 404 page: "404 Oh no! Page not found: /user/a168770b-d50e-4b43-b0f2-456c8f58c5fa An error occurred while responding to your request. If you believe this to be a bug, please report it. Try signing in and see if it resolves the issue." - No log errors - Non-admin users (in groups allowed through via the Authentik provider policy) see this error as well. Seems that it doesn't create a user directory appropriately for users created with OIDC - Also noticed that under Username -> Account Settings, the "Home", "Security", and "Settings" menus are completely blank. Not sure if this is expected or not with the early state of this tool, but may be related if not expected.
yindo closed this issue 2026-02-17 17:06:03 -05:00
yindo commented 2026-02-17 17:06:03 -05:00
Author
Owner
Copy Link
Copy Source

@DecDuck commented on GitHub (Aug 1, 2025):

I think these are all expected errors fortunately, we haven't implemented these pages. The user profiles/customisation is a bit bare bones at the moment unfortunately.

@DecDuck commented on GitHub (Aug 1, 2025): I think these are all expected errors fortunately, we haven't implemented these pages. The user profiles/customisation is a bit bare bones at the moment unfortunately.
yindo commented 2026-02-17 17:06:03 -05:00
Author
Owner
Copy Link
Copy Source

@tomorrow-nf commented on GitHub (Aug 1, 2025):

Ah that makes sense, no worries!

@tomorrow-nf commented on GitHub (Aug 1, 2025): Ah that makes sense, no worries!
yindo changed title from [Bug?] User profile page not found with OIDC to [GH-ISSUE #161] [Bug?] User profile page not found with OIDC 2026-06-05 14:21:17 -04:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
confirmed
duplicate
feature
feature
good first issue
needs-triage
pull-request
Mirrored from GitHub Pull Request
 qol
support
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Drop-OSS/drop#76
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?