Merge pull request #106 from Real-Dev-Squad/cookie-readme

Document about getting cookie in local

Author: ankurnarkhede

CONTRIBUTING.md

@@ -83,9 +83,10 @@ The following project structure should be followed:
 ```
 
 ## Generating Authentication Token
+- Run the project locally, make sure the server is listening to requests
 - Navigate to `https://github.com/login/oauth/authorize?client_id=<GITHUB_CLIENT_ID>`
-- Authorize the application.
-- Copy the response cookie named `rds-session` from the redirected request from the API.
+- Authorize the application
+- Copy the response cookie named rds-session from the redirected request <HOST>/auth/github/callback?code=<SOME_AUTOGENERATED_CODE>
 - Use the cookie for authenticated routes in the API.
 - For non-production environments, authentication is also supported with the `Authorization` header.
 - Authorization header: `Authorization: Bearer <token>`
@@ -96,4 +97,3 @@ The following project structure should be followed:
 - Every pull request should have associated issue(s) on our [issue tracker](https://github.com/Real-Dev-Squad/website-backend/issues).
 - For any non-trivial fixes and features, unit and integration tests must be added. The PR reviewer should not approve/merge PR(s) that lack these.
 - The PR(s) should be merged only after the CI passes.
-