Is a generic approach to "make sure people log in as some user" possible? #2
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
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?
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) ?