Investigate approaches for adding OAuth2/OIDC support
- Dominant language
- TypeScript
- Stars
- 481
- Forks
- 108
- Avg merge
- 6d 8h
- Merged PRs (30d)
- 5
Description
## Goal
Investigate possible approaches to add OAuth2 and/or OIDC authentication support to Graph Explorer. Determine how authentication flows would integrate with the existing proxy server architecture, what libraries or frameworks are best suited, and what trade-offs exist between different approaches.
Key questions to answer:
- Which OAuth2/OIDC flows are appropriate for Graph Explorer (e.g. Authorization Code with PKCE, Client Credentials)?
- How would token management work given the client-side architecture and backend proxy?
- What identity providers should be targeted (e.g. Amazon Cognito, Okta, Azure AD, generic OIDC)?
- How would authenticated requests be forwarded to the graph database?
- What changes are needed in the proxy server vs. the client?
## Expected Outcome
- A written recommendation documenting the viable approaches with pros and cons
- A rough estimate of effort for the recommended approach
- A tasked-out epic if the spike confirms feasibility
## Related Issues
_None_
---
> [!IMPORTANT]
> If you are interested in working on this issue, please leave a comment.
> [!TIP]
> Please use a 👍 reaction to provide a +1/vote. This helps the community and maintainers prioritize this request.
Contributor guide
Assessment
This issue has not been assessed yet.