auth feature in fpm tracker

[amitu]

Status: In Progress

Author: Wasif

Code PR: #589
Doc PR: Pending

TODOS

• get identities api
• integration of auth with fpm

---

Discord

• basic login
• discord-server:
• discord-channel:
• discord-role: <server-id#role-name>
  Discussion: fpm-auth: Discord OAuth Integration #663

---

Telegram

• Discussion: fpm-auth: Telegram OAuth Integration #648

---

Google

• Discussion: fpm-auth: Google OAuth Integration #655

---

Github

• basic login
• github-username
• github-stars: ftd-lang/ftd
• integration with fpm
• github-follows:
• github-follows-account:
• github-sponsors:
• github-team:

Static: github-username

This would be always present if the user is logged in.

Dynamic: github-stars=<repo-name>

If this is asked, it would be returned as part of get-identities only if the currently logged in user has starred the repo.

Dynamic: github-follows=<repo-name>

If this is asked, it would be returned as part of get-identities only if the currently logged in user has followed the repo.

Eg if github-follows=ftd-lang/ftd is requested, if the logged in user follows the repo ftd-lang/ftd then it should be returned.

Dynamic: github-follows-account=<account-name>

If this is asked, it would be returned as part of get-identities only if the currently logged in user has followed the account.

Eg if github-follows=ftd-lang/ftd is requested, if the logged in user follows the repo ftd-lang/ftd then it should be returned.

Dynamic: github-sponsors=<account-name>

If this is asked, it would be returned as part of get-identities only if the currently logged in user has sponsored the account.

Eg if github-follows=ftd-lang is requested, if the logged in user sponsors the account ftd-lang.

Slack

• basic login
• slack-org:
• slack-channel: <org-name#channel-name>

Gmail

• basic login

Twitter

GitLab

Yahoo

Microsoft

LinkedIn

Instagram

Facebook

Dropbox

DigitalOcean

BitBucket

Apple

Amazon

Okta

Pintrest

Twitch

WeChat

Zoho

Doorkeeper

Baidu

Tiktok

[wasif1024]

[AbrarNitk]

@wasif1024 move this to the https://github.com/orgs/FifthTry/discussions/108

[wasif1024]

Ok

[AbrarNitk]

GitHub Integration

GitHub Resource APIs

• Login
• Watch
• Follows
• User Details
• GitHub Teams
• GitHub Sponsors

[AbrarNitk]

@wasif1024 please list down all the GitHub APIs here.

[wasif1024]

• Login

Github Auth Url: https://github.com/login/oauth/authorize
Github TokenUrl: https://github.com/login/oauth/access_token

• User Details

Github User Details:https://api.github.com/user

• Starred

https://api.github.com/user/starred

• Watch

https://api.github.com/user/subscriptions

• Follow

https://api.github.com/user/following

[AbrarNitk]

Storing provider data in Cookie

@wasif we can also store user information in a cookie, mostly every API needs the user details and we are calling API every time to fetch the user details. We can store <provider-short-name>-ud in cookies instead of access_token. Provider data will be encrypted by the fpm server.

Discussion with @amitu:

We will store a different cookie for each auth provider.
For GitHub: gh-ud, Discord: dc-ud, Telegram: tl-ud.

For Github

Cookie name: gh-ud

  {
     token: <token from github>
     user_name: <name of the user, fetched from user-details api>
     ...some other details if needed
  }

[wasif1024]

Yes initially i stored access token,user email and user name in cookies so that we do not need to call user detail api again and again. But according to @amitu instructions i am storing access token in cookies. So we can again save it in cookies and use that

[wasif1024]

Yes if we want to save mutiple oauth login info then we can save information based on provider in cookies

[wasif1024]

Now we need to save user name in cookies right?

[AbrarNitk]

Yes

[amitu]

@AbrarNitk lets get on a call to discuss this.

[wasif1024]

Discord pull request.
#670

[wasif1024]

Twitter pull request
#676

[wasif1024]

I have pushed code for twitter-liking and twitter-followers.
For twitter-liking we have implemented functionality to allow only specific users who have liked a tweet.
Input parameters
twitter-liking: 1603372330595807233
For twitter-followers we have implemented functionality to allow only specific users who have followed given user id.
Input parameters
twitter-followers: 1512403291665321994

[wasif1024]

Today i have completed following functionalities.
1: Now i have changed input parameters of
twitter-followers and twitter-follows where we do not need to pass Id of user but we can simply pass username ike examples given below
twitter-followers: VillageBoota
twitter-follows: VillageBoota
Secondly i have integrated different apis given below
One Api is related to twitter following. For this api i have implemented logic in a way that logged in user must be followed by input user to access a page
I have implemented another api that implements logic to allow logged in user to access a page if he has retweeted a tweet using tweet id.
Another api that i have implemented is related to twitter space which checks that logged in user must by ticket of a space to access a page
Input Params
twitter-followers: VillageBoota
twitter-follows: VillageBoota
twitter-space: 1LyxBqkaWpWJN
twitter-retweet: 1604478024346472452

[wasif1024]

Documentation links
Github

https://docs.google.com/document/d/1qjwE0AjWTm1JO4YAgadasaOSg6hHClHgYJ7TzPq3FMk/edit

Telegram

https://docs.google.com/document/d/1Jggr8kAu04zPo8r8FnIZvJxlcZvgLLamZ4XOuoMLtgw/edit?usp=drive_web&ouid=104328136860868132344

Twitter

https://docs.google.com/document/d/1u5JjZeO2Jkl6Qh-h3h6QEb8bRRnpP4HfZVzOMsgFqzQ/edit?usp=drive_web&ouid=104328136860868132344

Discord

https://docs.google.com/document/d/1vliqWsp865PQWdc7XAwMGlJqGlwCCHlCcH7V1vd3HEo/edit?usp=drive_web&ouid=104328136860868132344