Authentication #12
Labels
No labels
Compat
Breaking
Kind
Bug
Kind
Documentation
Kind
Enhancement
Kind
Feature
Kind
Meta
Kind
Renovate
Kind
Repository
Kind
Security
Kind
Testing
Kind
Tooling
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Out of Scope
Reviewed
Won't Fix
Size
L
Size
M
Size
S
Size
XL
Size
XS
Status
Abandoned
Status
Blocked
Status
Need More Info
No milestone
No project
No assignees
2 participants
Notifications
Total time spent: 37 minutes 6 seconds
Due date
cswimr
37 minutes 6 seconds
No due date set.
Blocks
#2 API Base
cswimr/LookingGlass
#13 Permissions
cswimr/LookingGlass
Reference: cswimr/LookingGlass#12
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?
What should the authentication system look like?
Currently,
User
has the following schema:What access should each user have? Should they be able to request any moderation in the database, or should they only be able to request moderations attributed to them? Should moderation retrieval not require authentication at all, meaning only submitting new moderations would require authentication?
So I think some thing like
<DISCORDID>.<RANDOMALPHANUMERICS>
, and so I can track stuff like API abuse, and usage, everyone should need a token.What about this, @MYHM?
Anyone with a token can look up any moderation on an id, but only some tokens can add them, or modify them.
So, do we want read/write or read/edit/create?
Edit: This is what I have now.
Yeah I think this would be best, so that way I can have people who can redact things if situations change, and I can't have a malicious actor remove all of them stuff like that, but still having that finer control of things