feat: Add BrightData Unlocker tool component #5075
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,40 +1,40 @@ | ||
| ### Responsible Disclosure Policy | ||
|
|
||
| At Flowise, we prioritize security and continuously work to safeguard our systems. However, vulnerabilities can still exist. If you identify a security issue, please report it to us so we can address it promptly. Your cooperation helps us better protect our platform and users. | ||
|
|
||
| ### Vulnerabilities | ||
|
|
||
| The following types of issues are some of the most common vulnerabilities: | ||
|
|
||
| - Clickjacking on pages without sensitive actions | ||
| - CSRF on unauthenticated/logout/login pages | ||
| - Attacks requiring MITM (Man-in-the-Middle) or physical device access | ||
| - Social engineering attacks | ||
| - Activities that cause service disruption (DoS) | ||
| - Content spoofing and text injection without a valid attack vector | ||
| - Email spoofing | ||
| - Absence of DNSSEC, CAA, CSP headers | ||
| - Missing Secure or HTTP-only flag on non-sensitive cookies | ||
| - Deadlinks | ||
| - User enumeration | ||
|
|
||
| ### Reporting Guidelines | ||
|
|
||
| - Submit your findings to https://github.com/FlowiseAI/Flowise/security | ||
| - Provide clear details to help us reproduce and fix the issue quickly. | ||
|
|
||
| ### Disclosure Guidelines | ||
|
|
||
| - Do not publicly disclose vulnerabilities until we have assessed, resolved, and notified affected users. | ||
| - If you plan to present your research (e.g., at a conference or in a blog), share a draft with us at least **30 days in advance** for review. | ||
| - Avoid including: | ||
| - Data from any Flowise customer projects | ||
| - Flowise user/customer information | ||
| - Details about Flowise employees, contractors, or partners | ||
|
|
||
| ### Response to Reports | ||
|
|
||
| - We will acknowledge your report within **5 business days** and provide an estimated resolution timeline. | ||
| - Your report will be kept **confidential**, and your details will not be shared without your consent. | ||
|
|
||
| We appreciate your efforts in helping us maintain a secure platform and look forward to working together to resolve any issues responsibly. | ||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,36 @@ | ||
| import { INodeParams, INodeCredential } from '../src/Interface' | ||
|
|
||
| class BrightDataApi implements INodeCredential { | ||
| label: string | ||
| name: string | ||
| version: number | ||
| description: string | ||
| inputs: INodeParams[] | ||
|
|
||
| constructor() { | ||
| this.label = 'BrightData API' | ||
| this.name = 'brightDataApi' | ||
| this.version = 1.0 | ||
| this.description = 'Go to https://brightdata.com/, navigate to settings, and create an API key or copy your existing one.' | ||
| this.inputs = [ | ||
| { | ||
| label: 'BrightData API Key', | ||
| name: 'brightDataApiKey', | ||
| type: 'password', | ||
| placeholder: '<BRIGHTDATA_API_KEY>', | ||
| description: 'Your BrightData API key (Bearer token)' | ||
| }, | ||
| { | ||
| label: 'Zone', | ||
|
There was a problem hiding this comment. how to find this? please add docs link to the description. Refer to other credential how this is done There was a problem hiding this comment. will add references to the website |
||
| name: 'brightDataZone', | ||
| type: 'string', | ||
| default: 'web_unlocker1', | ||
| placeholder: 'web_unlocker1', | ||
| description: 'Proxy Zone - Place your unlocker zone name here', | ||
| optional: true | ||
| } | ||
| ] | ||
| } | ||
| } | ||
|
|
||
| module.exports = { credClass: BrightDataApi } | ||
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can we keep unrelated changes out of this PR?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do you just want the commit not to contain it?