Need advice on LinkedIn OAuth architecture
OAuth related
We have two LinkedIn Developer apps:
- App A for user sign-in
- App B approved for Community Management API (analytics scopes), because LinkedIn required this product to be isolated
Question: what’s the cleanest way to handle tokens without manual refresh logic?
Specifically:
- LinkedIn tokens are app-bound, so App A tokens can’t call App B endpoints
- We want one user account in our app, but two LinkedIn OAuth connections
- We use Better Auth today (single LinkedIn provider)
Has anyone implemented this pattern with Better Auth (or similar), e.g. second LinkedIn connection via generic OAuth + automatic
refresh? Any gotchas or recommended approach?
- App A for user sign-in
- App B approved for Community Management API (analytics scopes), because LinkedIn required this product to be isolated
Question: what’s the cleanest way to handle tokens without manual refresh logic?
Specifically:
- LinkedIn tokens are app-bound, so App A tokens can’t call App B endpoints
- We want one user account in our app, but two LinkedIn OAuth connections
- We use Better Auth today (single LinkedIn provider)
Has anyone implemented this pattern with Better Auth (or similar), e.g. second LinkedIn connection via generic OAuth + automatic
refresh? Any gotchas or recommended approach?
