Productivity / Enterprise
WordPress.com / Jetpack OAuth
WordPress.com authorization may target one blog or broader scopes, and token inspection requires both client ID and token query parameters.
Specialised flow
Manual provider setup
WordPress.com authorization may target one blog or broader scopes, and token inspection requires both client ID and token query parameters.
Required inputs
- clientId and clientSecret
- exact redirectUri
- scope list and optional blog ID or URL
- authorization code
- 01UnderstandReview why this provider needs a specialized setup path.
- 02CollectGather the required provider-specific fields.
- 03Run setupComplete the provider flow outside the generic OAuth form.
- 04ValidateUse the checklist to confirm token and metadata handling.
What this workflow can do
- Manual provider checklist
- Provider-specific inputs
- Generic OAuth form
Before starting
- clientId and clientSecret
- exact redirectUri
- scope list and optional blog ID or URL
- authorization code
Result handling
- Use the checklist to complete provider-specific setup outside the generic form.
- Anonymous OAuth Hub workflows do not store secrets, tokens, or provider payloads.
Troubleshooting
- Use Authorization Code for production; implicit and password grants are not appropriate for this tool.
- Jetpack-connected sites use WordPress.com OAuth but site and scope selection still affect access.
Provider checklist
- Register the application in WordPress.com Applications Manager.
- Choose least-privilege scopes and optional single-blog targeting.
- Exchange the code server-side with the exact redirect URI.
- Inspect the token with /oauth2/token-info using both client_id and token.