Is a generic approach to "make sure people log in as some user" possible? #2

Open
opened 2026-03-01 19:27:47 +00:00 by tom · 0 comments
Owner

I did a test with my audiobookshelf, and using "simple-auth" works - but it needs to know quite a lot about the application.
For example, the login flow will create a bearer token - but not store/send the "someone is logged in" cookie.

I suspect there will be a wide variety of silly ways things might do it, so a generic approach might not be feasible. Perhaps it can be broken out into app-specific config (like horrible WAF rules) ?

I did a test with my audiobookshelf, and using "simple-auth" works - but it needs to know quite a lot about the application. For example, the login flow will create a bearer token - but not store/send the "someone is logged in" cookie. I suspect there will be a wide variety of silly ways things might do it, so a generic approach might not be feasible. Perhaps it can be broken out into app-specific config (like horrible WAF rules) ?
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
spoons.technology/core-ingress#2
No description provided.