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

Scope: StaticMultiSelect #803

Closed
kanarelo opened this issue Mar 14, 2023 · 2 comments
Closed

Scope: StaticMultiSelect #803

kanarelo opened this issue Mar 14, 2023 · 2 comments

Comments

@kanarelo
Copy link
Contributor

Is your feature request related to a problem? Please describe.
I would love if the user can change/modify the scope that the Keys they provide match.

Describe the solution you'd like
Sometimes, a user may have several (pairs of) API keys for security purposes. Example, one for reading mail only and another for sending.

As it is, when you define your auth property for pieces, you need to provide a scope array. The provided array can (should?) be the full list of scope, and allow the user to select the scope they need at time of making connection.

Describe alternatives you've considered
The alternative is to provide the list of narrowed down scopes.

can help solve #802

@abuaboud abuaboud added the 🤷‍♂️🤷‍♀️ untriaged Need attention from maintainer in activepieces label Mar 28, 2023
@abuaboud
Copy link
Contributor

Related to your feature request, it would be great if users could modify the scope for the keys they provide. However, asking the user to select the required scopes could be confusing and cause issues.

For instance, with Google Sheets trigger, the Google Drive list files scope is required to construct the options in dropdown, which may not be straightforward for the user to understand.

As a workaround, users can provide their own app credentials and edit the pieces at their own responsibility.

For now, I am going to close the issue, but feel free to reopen it later.

@abuaboud abuaboud added ⭐ enhancement New feature or request and removed 🤷‍♂️🤷‍♀️ untriaged Need attention from maintainer in activepieces ⭐ enhancement New feature or request labels Mar 29, 2023
@github-actions
Copy link

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If this issue is continuing with the lastest stable version of Activepieces, please open a new issue that references this one.

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

2 participants