OAuth defines four roles:

resource owner
An entity capable of granting access to a protected resource.
When the resource owner is a person, it is referred to as an
end-user.

resource server
The server hosting the protected resources, capable of accepting
and responding to protected resource requests using access tokens.

client
An application making protected resource requests on behalf of the
resource owner and with its authorization. The term "client" does
not imply any particular implementation characteristics (e.g.,
whether the application executes on a server, a desktop, or other
devices).

authorization server
The server issuing access tokens to the client after successfully
authenticating the resource owner and obtaining authorization.

The interaction between the authorization server and resource server
is beyond the scope of this specification. The authorization server
may be the same server as the resource server or a separate entity.
A single authorization server may issue access tokens accepted by
multiple resource servers.

Reference: https://tools.ietf.org/html/rfc6749#section-1.1
@akshayarora2009 @crypton3535

Please populate this spreadsheet with dummy data for testing the feedback portal: https://docs.google.com/spreadsheets/d/1JEuTgP2yyVqzz-YMHSEKSH1QSyoDOBgYtNXpRJZYzFM/edit?usp=sharing

Put the necessary headings in bold, and data below it. Make sure we complete it by tonight (Around 20 values in each table).
Comment below if you have any doubt.

SSH works on port 22 by default. However, this port is blocked by the college firewall by default.

The solution is to SSH on port 443, which is not blocked.

In the file /etc/ssh/sshd_config , add the following line:

Port 443

To connect over port 443, just use the -p 443 flag. eg. ssh -p 443 <user>@<host>
Let me know if you have any problems.

FYI: @Princedhaliwal @crypton3535 @pola07 @kvibhore

For now, I have defined ADMIN with access level of 1 (on scale of 1-10) and UNKNOWN user with 10.
What about students, teachers, Society heads, CR's etc?

Let's set up our servers on Digital Ocean.

@crypton3535 , I hope you have the credits set up in your account.

Steps: Just log in to digital ocean, click on create droplet and then choose the following options:

OS: Ubuntu 16.04 X64
Size: $10/month plan (don't worry, we'll delete it much earlier and will be charged less)
Data Center region: Bangalore, India
Leave everything else as it is, but choose a suitable hostname. (eg: auth-portal)

Create your droplet. You will get a mail telling you your root password.

Then create users. Do not work everytime with root user. You should work with your own user with sudo privileges.

Here's how to do that: https://www.digitalocean.com/community/tutorials/how-to-create-a-sudo-user-on-ubuntu-quickstart

Cheers. Let me know when you are done.

Currently I have not written code for registration of services. We can't hard code them into the database. Instead there should be a registration portal where new services can request themselves and admin can approve or disapprove requests. Or there should be a portal for admin, where he can add new service to the database.