search

SuffolkLITLab / docassemble-ALDashboard

A frontend to a few common administrative backend functions that aren't built-in to Docassemble
MIT License
8 stars 0 forks source link

Improvements to package install and browsing #141

Closed nonprofittechy closed 5 months ago

nonprofittechy commented 5 months ago

Fix #119 Fix #64

Adds a simple dashboard to let you view installed packages and the YAML files in them, and then run those packages. Makes it unnecessary to create a link to run the package.

Also adds the ability to add a private access token to the global configuration and to use a private access token when installing a package from GitHub using the Dashboard.

gitguardian[bot] commented 5 months ago

⚠️ GitGuardian has uncovered 3 secrets following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secrets in your pull request
| GitGuardian id | GitGuardian status | Secret | Commit | Filename | | | -------------- | ------------------ | ------------------------------ | ---------------- | --------------- | -------------------- | | [11053455](https://dashboard.gitguardian.com/workspace/175765/incidents/11053455?occurrence=135275149) | Triggered | Basic Auth String | 2246e74ec8202e62ba3fcde4666f6df3f1f3ca53 | docassemble/ALDashboard/aldashboard.py | [View secret](https://github.com/SuffolkLITLab/docassemble-ALDashboard/commit/2246e74ec8202e62ba3fcde4666f6df3f1f3ca53#diff-4843303e71b988348c489b7f6c97a0e1a9e85f2a324bdb196463665c5a957cd4R73) | | [11053455](https://dashboard.gitguardian.com/workspace/175765/incidents/11053455?occurrence=135275210) | Triggered | Basic Auth String | 800a1e47a9acba0fcab026813e08fe5007bba6a4 | docassemble/ALDashboard/aldashboard.py | [View secret](https://github.com/SuffolkLITLab/docassemble-ALDashboard/commit/800a1e47a9acba0fcab026813e08fe5007bba6a4#diff-4843303e71b988348c489b7f6c97a0e1a9e85f2a324bdb196463665c5a957cd4L73) | | [11053470](https://dashboard.gitguardian.com/workspace/175765/incidents/11053470?occurrence=135275211) | Triggered | Basic Auth String | 800a1e47a9acba0fcab026813e08fe5007bba6a4 | docassemble/ALDashboard/aldashboard.py | [View secret](https://github.com/SuffolkLITLab/docassemble-ALDashboard/commit/800a1e47a9acba0fcab026813e08fe5007bba6a4#diff-4843303e71b988348c489b7f6c97a0e1a9e85f2a324bdb196463665c5a957cd4R73) |
🛠 Guidelines to remediate hardcoded secrets
1. Understand the implications of revoking this secret by investigating where it is used in your code. 2. Replace and store your secrets safely. [Learn here](https://blog.gitguardian.com/secrets-api-management?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment) the best practices. 3. Revoke and [rotate these secrets](https://docs.gitguardian.com/secrets-detection/secrets-detection-engine/detectors/generics/basic_auth_string#revoke-the-secret?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment). 4. If possible, [rewrite git history](https://blog.gitguardian.com/rewriting-git-history-cheatsheet?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment). Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data. To avoid such incidents in the future consider - following these [best practices](https://blog.gitguardian.com/secrets-api-management/?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment) for managing and storing secrets including API keys and other credentials - install [secret detection on pre-commit](https://docs.gitguardian.com/ggshield-docs/integrations/git-hooks/pre-commit?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment) to catch secret before it leaves your machine and ease remediation.

🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.

nonprofittechy commented 5 months ago

⚠️ GitGuardian has uncovered 1 secret following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secret in your pull request 🛠 Guidelines to remediate hardcoded secrets 🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.

Note that this is an example credential, not a real one. But I'll redact to help avoid future false positives.