Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Authentication with PKCE #4897

Open
gwintzer opened this issue Nov 8, 2024 · 2 comments
Open

Authentication with PKCE #4897

gwintzer opened this issue Nov 8, 2024 · 2 comments
Labels
enhancement New feature or request help wanted Community contributions are especially encouraged for these issues. triaged Issues labeled as 'Triaged' have been reviewed and are deemed actionable.

Comments

@gwintzer
Copy link

gwintzer commented Nov 8, 2024

Is your feature request related to a problem? Please describe.

The current authentication methods in OpenSearch Dashboard do not support PKCE, which is required by our OAuth2 provider. This limitation prevents us from securely authenticating users and integrating with our existing authentication infrastructure.

Describe the solution you'd like

I would like to see the implementation of PKCE (Proof Key for Code Exchange) authentication in OpenSearch Dashboard to comply with our OAuth2 provider's requirements. This would enhance security and allow seamless integration.

Describe alternatives you've considered

Currently, we have considered using other authentication methods, such as standard OAuth2 flows without PKCE, but these do not meet our security standards. We have also explored alternative dashboards, but we prefer to continue using OpenSearch Dashboard if possible.

Additional context

Implementing PKCE would align OpenSearch Dashboard with modern security practices and improve user experience. Documentation or examples of PKCE implementation in similar tools could also be beneficial.

I would add that PKCE becomes mandatory with Oauth2.1. See https://erkanyasun.medium.com/oauth-2-1-vs-oauth-2-0-a-detailed-tutorial-882b7cc7bd23 for example

@gwintzer gwintzer added the enhancement New feature or request label Nov 8, 2024
@Hailong-am
Copy link
Contributor

@opensearch-project/admin can you transfer this to security plugin?

@gaiksaya gaiksaya transferred this issue from opensearch-project/OpenSearch-Dashboards Nov 12, 2024
@github-actions github-actions bot added the untriaged Require the attention of the repository maintainers and may need to be prioritized label Nov 12, 2024
@cwperks cwperks added triaged Issues labeled as 'Triaged' have been reviewed and are deemed actionable. help wanted Community contributions are especially encouraged for these issues. and removed untriaged Require the attention of the repository maintainers and may need to be prioritized labels Nov 18, 2024
@cwperks
Copy link
Member

cwperks commented Nov 18, 2024

[Triage] This sounds like a good feature request. Marking this as Triaged and Help Wanted.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request help wanted Community contributions are especially encouraged for these issues. triaged Issues labeled as 'Triaged' have been reviewed and are deemed actionable.
Projects
None yet
Development

No branches or pull requests

3 participants