Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

API access for external developers #68

Open
aahnik opened this issue Apr 26, 2024 · 0 comments
Open

API access for external developers #68

aahnik opened this issue Apr 26, 2024 · 0 comments
Assignees
Labels
backend future May do in future

Comments

@aahnik
Copy link
Contributor

aahnik commented Apr 26, 2024

Any developer who wishes to implement their own client, needs to host the API themselves.

For enhanced security, and identification, the cookies are set with Same-Site:Strict policy. The frontend must the same domain name of the backend. (deploy on a different sub-domain).

In future if we wish to support other developers (non-official clients), to use the API hosted by us. We will follow a streamlined approach of

  • issuing API keys and secrets to developers, for specific set of scopes requested by them.
  • allowing the developer to register their domain
  • the list of allowed domains will be set in our db, and our CORS policy will be defined on the fly using a callback function
  • creating our own oauth consent screens, for scopes requested by other developers. So the external developer's code, can access an user's resource only with their authorization.

Read more about cors same site options.

@aahnik aahnik added future May do in future backend labels Apr 26, 2024
@aahnik aahnik self-assigned this Apr 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backend future May do in future
Projects
None yet
Development

No branches or pull requests

1 participant