Clean up authentication system #56629
Labels
No Label
legacy project
Infrastructure: Websites
legacy project
Pillar
legacy project
Pillar Framework
legacy project
Pillar Website
Priority::High
Priority::Low
Priority::Normal
Status::Archived
Status::Confirmed
Status::Resolved
Type::Bug
Type::Design
Type::Patch
Type::Report
Type::To Do
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: archive/pillar#56629
Loading…
Reference in New Issue
Block a user
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?
The current authentication system is a big pile of microwave spaghetti (not to be confused with delicious spaghetti) and should be cleaned up.
session['user_id']
is an authentication token.session['user_id']
is sent as-is to the web browser. This is like sending a password back and forth all the time.Authorization
header or do a CSRF check, but don't do both.UserClass
instance can be created empty with only an authentication token, or filled with information from the database. It's unclear which one is used in which situation.Added subscribers: @dr.sybren, @fsiddi