LinkedIn OAuth
Enter a valid instance URL (https:// is required unless it is localhost).
cinatra install cinatra-ai/linkedin-oauth-connector
LinkedIn OAuth
Configure the LinkedIn app your workspace uses to connect member and organization accounts. Create one LinkedIn developer app, save its Client ID and Client secret here, and every user can then connect their own LinkedIn account through the LinkedIn connector. This connector is the credentials half of the LinkedIn integration: it owns the OAuth app setup form and stores the workspace-wide credentials, while the LinkedIn connector handles individual user authentication.
Setup. In the LinkedIn Developer Portal, create a developer application. Copy the Client ID and Client secret, then paste them into the LinkedIn OAuth setup page inside Cinatra. If the redirect URI is already stored in the connector configuration, the setup page displays it with a copy button — register that exact URI in your LinkedIn developer app. Credentials are write-only once saved; the Client secret is never sent to the browser.
Credential storage. The connector saves credentials under a shared connector-config key. Saving new credentials preserves connected user accounts, the redirect URI, and other fields already written by the LinkedIn connector — partial saves never wipe connected accounts.
Required permissions. The save action is gated by the manage permission (org owners, org admins, and platform admins). The setup page itself is accessible to any user with access to the extension dispatch route.
Troubleshooting. If users cannot connect their LinkedIn account, confirm that both the Client ID and Client secret show as configured (the status badge reads "Configured"). If only one field is saved, the OAuth flow cannot complete — save both values. If the Authorized Redirect URI does not appear on the setup page, confirm that the redirect URI has been stored in the connector configuration. Verify that the URI in your LinkedIn developer app matches the URI on the setup page exactly.
Works with
Capabilities
- Save the LinkedIn app's Client ID and Client secret in one place
- Power the per-user LinkedIn account connect flow without configuring credentials per user
- Rotate the workspace's LinkedIn OAuth credentials from a single setup page
- Display the Authorized Redirect URI with a one-click copy button for LinkedIn app registration
- ci: add truthful-attribution-gate in WARN (advisory) mode (#8)
- ci: adopt the reusable extension->host IoC conformance gate (org-wide rollout) (#9)
- ci: tag-driven GitHub release on v* (#10)
- ci: adopt secret-scan-gate (#11)
- docs(readme): expand README to the org standard (#12) (#13)
- ci(ui-gate): ramp raw-JSX block warn->error (0 warnings clean) (#14)
- ci(ui-gate): re-vendor preset with Block-C (dynamic-import ban) + bump pin to v0.1.1 (#15)
- chore: strip private engineering-tracker refs from public source (#17)
- feat(setup): link 'LinkedIn developer app' to the developer portal (#16) (#20)
- chore: strip private tracker references from workflow comments (#21)
- ci(release): re-pin release.yml to the release-approval wall (.github@v0.1.1) (#23)
- Configure Renovate (#1)
- Do not redirect from the save action (avoids NEXT_REDIRECT swallow) (#2)
- ci(release): grant contents: write + pin reusable workflow to .github HEAD (#4)
- ci: repin reusable release workflow (immutable-safe decoration + corrected build-input provisioning) (#5)
- release: bump linkedin-oauth-connector 0.1.0 -> 0.1.1 + repin release workflow (#6)
- release: exclude src/tests from publish tarball (packlist gate #56) (#7)
- Unreleased
- fix(setup): remove the extension-rendered connection-status pill (#24)
- fix: refresh setup page after saving so stored credentials render (#25)
- chore(manifest): backfill cinatra.sdkAbiRange ^2 (#26)
- fix: echo the canonical Nango OAuth redirect URI on the LinkedIn setup page (#28)
- fix(manifest): grant the nango host port (required by the redirect-URI echo) (#29)
- chore(deps): declare cinatra.consumes for closure-gate enrollment (#30)
- chore(deps): align zod pin to ^4.4.3 (#31)
More from Cinatra
Connect Plane to Cinatra so your agents can create, update, and track projects and work items in your Plane workspace.
Enter a valid instance URL (https:// is required unless it is localhost).
cinatra install cinatra-ai/plane-connector
See every external MCP client that has signed in to your Cinatra workspace and manage their access. Cinatra exposes its agents over the Model…
Enter a valid instance URL (https:// is required unless it is localhost).
cinatra install cinatra-ai/mcp-client-connector
Register external Model Context Protocol servers so every Cinatra agent and package can call their tools. This admin connector carries the external-MCP server management…
Enter a valid instance URL (https:// is required unless it is localhost).
cinatra install cinatra-ai/mcp-server-connector
Reviews
There are no reviews yet.