Credentials Standards #3
Labels
No Label
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: public/punchin#3
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
All forms of authentication with third party services (such as a Git forge, an IMAP server, etc.) should require the creation of OAuth clients or otherwise scope-limited tools to ensure the management of resources does not extend beyond what PunchIn requires. For example, a PunchIn configuration intended to work specifically with Icepick should only have write access to issues against the Icepick repository. This can likely be done by creating an OAuth client for Forgejo and requesting permission limited to the repository, but this implementation may require some form of webserver for OAuth callbacks.
In addition, credentials should be managed using some form of credential handler that does not expose the credentials in plaintext, ideally using some wrapper that wraps authentication tokens in OpenPGP encrypted blobs and decrypts them on-demand using GPG-Agent w/ Split GPG or some other OpenPGP Card backend..
OAuth is not a strict requirement if a Forgejo credential can be created with a limited issue scope.