Opened 4 weeks ago
Last modified 4 weeks ago
#64850 new enhancement
Connectors: Extend bridge for JS custom card rendering and non-API-key authentication support
| Reported by: |
|
Owned by: | |
|---|---|---|---|
| Milestone: | Future Release | Priority: | normal |
| Severity: | normal | Version: | trunk |
| Component: | Administration | Keywords: | |
| Focuses: | javascript | Cc: |
Description
Follow-up to #64791, which completed the PHP side of the Connectors extensibility API (WP_Connector_Registry, wp_connectors_init action, wp_get_connectors() and related read functions). The remaining work is on improving integration with the JS side.
Every connector currently renders the same default card (API key input + save/remove). Plugins that need custom UI — OAuth flows, token status, multi-field forms — have no supported path. An experimental JS API is available to register a custom card renderer keyed to a connector ID.
Additionally, the PHP registry accepts any authentication.method, but the Connectors screen JS currently renders nothing for non-api_key connectors. These should surface at minimum as a generic card with a credentials_url link, or a custom renderer if the plugin provides one via item 1. This should cover methods such as OAuth, app passwords, and bearer tokens.
References
- #64730 — original Connectors screen
- #64791 — PHP extensibility API
- wordpress-develop#11175, wordpress-develop#11227
- Gutenberg#75833, Gutenberg#76014