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

Security concerns #5

Open
joshuapease opened this issue May 20, 2024 · 0 comments
Open

Security concerns #5

joshuapease opened this issue May 20, 2024 · 0 comments

Comments

@joshuapease
Copy link
Contributor

Nevin raised some potential concerns about security.

Mainly... we have read access on the database and all child pages.

If someone has access to the API key, they could view our full list of clients, their plugin version and other sensitive data.

Notion doesn't make it particularly easy to spin up multiple keys for one integration. You have to create one integration per site and attach that integration to the inventory database.

Possible solution:

  • Give the integration "write only" access.
  • Manually create a Notion DB row for the site
  • For each site, you provide the ID of the row that the site can write to.

The downsides of this method:

  • This is a bummer for tracking multiple environments per site. You'd have to create a row ID per site, per environment.
  • For multisite projects, you'd either have to create a row ID per site (and map site handle -> row). Or we would just write to a single row and store data about the sites in a new column
    • This isn't the worst... because the plugin and server data would be identical for all multi-sites anyway.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant