Opened 3 months ago
#61089 new enhancement
Introduce a System to Store, Access, and Permit Use of External API Keys
| Reported by: |
Kpudlo
|
Owned by: | |
|---|---|---|---|
| Milestone: | Awaiting Review | Priority: | normal |
| Severity: | normal | Version: | |
| Component: | Administration | Keywords: | |
| Focuses: | Cc: |
Description
Right now, if we have a number of plugins that use the same API Key, such as Google Maps or reCaptcha, we may have to enter the same key on each plugin's settings page.
Ideally, if we could enter a name and API key for external services, similar to Application Passwords, and plugin developers could use these API Keys, it could help to reduce the redundancy of storing and maintaining these key.
On the Admin side, we could have a page that allows Admins to manage their keys, as well as approve or deny use of a key from a plugin. - This would be similar to how new apps downloaded to a phone have to request permission to use phone features before being able to use.
One concern would be determining a common naming convention/scheme for said keys.