Refer to users with an GUID (local part)
It is better to reference all users with a GUID to prevent unauthorized access to some components.
eg: User foo is registered, he registers a database. Next, he decides to remove his account foo. After a while, another user registers with username foo. Now that user has access to the database registered by the other foo user.
Blueprint information
- Status:
- Complete
- Approver:
- None
- Priority:
- Essential
- Drafter:
- None
- Direction:
- Approved
- Assignee:
- Lars Vierbergen
- Definition:
- Approved
- Series goal:
- Accepted for 2.x
- Implementation:
-
Implemented
- Milestone target:
-
2.0
- Started by
- Lars Vierbergen
- Completed by
- Lars Vierbergen
Related branches
Sprints
Whiteboard
Very important to prevent unauthorized access!
This changes architecture, so series 2.x
Database scheme is designed.
Good progress creating the new session class
The class is ready, currently deploying into the remaining of the panel
I think the local part is done.
New approach: static classes, waiting for implementation of that blueprint
Static classes OK for local: Implemented this one
Work Items
Dependency tree
* Blueprints in grey have been implemented.
