mirror of
https://github.com/nishchayp/DAMN.git
synced 2026-04-25 07:05:58 +03:00
[GH-ISSUE #4] Only allow users with verified email #6
Labels
No labels
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/DAMN#6
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?
Originally created by @nishchayp on GitHub (Nov 30, 2017).
Original GitHub issue: https://github.com/nishchayp/DAMN/issues/4
@ekamwalia commented on GitHub (Dec 9, 2017):
You mean something so that the first time a user tries to login, we verify if they actually have access before letting them make requests?
@nishchayp commented on GitHub (Dec 9, 2017):
The json that google OAuth2 api sends as response has a key-value pair "email_verified: true/false". If false then either we can restrict them or redirect them to some link to verify their email if such a service is provided by google.
@ekamwalia commented on GitHub (Dec 9, 2017):
There is another thing. Anyone can login with OAuth and make a request to for admin priviledges and droplet access
Should we place an admin authorization first so that every user can make many requests only after being approved by an admin
@nishchayp commented on GitHub (Dec 9, 2017):
A user is allowed to make only a single request, if that helps. Also how do you plan to implement it like IMO it would be added work for admins. But we can maybe think about it if everyone is fine with it and it brings some significant advantage.