Skip to content

Add proxy support for JWT realm. #114956

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

Closed
ajoliveira opened this issue Oct 16, 2024 · 1 comment · Fixed by #127337
Closed

Add proxy support for JWT realm. #114956

ajoliveira opened this issue Oct 16, 2024 · 1 comment · Fixed by #127337
Labels
>enhancement :Security/Authentication Logging in, Usernames/passwords, Realms (Native/LDAP/AD/SAML/PKI/etc) Team:Security Meta label for security team

Comments

@ajoliveira
Copy link

Description

Currently the JWT realm does not appear to support use of a proxy connection. No settings are exposed to allow configuration of such (potentially similar to the http.proxy.* settings available for OIDC for example.

Attempted workaround(s) of configuring host settings (HTTP_PROXY, HTTPS_PROXY, etc.) or via JVM arguments also do not work.

@ajoliveira ajoliveira added :Security/Authentication Logging in, Usernames/passwords, Realms (Native/LDAP/AD/SAML/PKI/etc) >enhancement needs:triage Requires assignment of a team area label labels Oct 16, 2024
@elasticsearchmachine elasticsearchmachine added the Team:Security Meta label for security team label Oct 16, 2024
@elasticsearchmachine
Copy link
Collaborator

Pinging @elastic/es-security (Team:Security)

@elasticsearchmachine elasticsearchmachine removed the needs:triage Requires assignment of a team area label label Oct 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
>enhancement :Security/Authentication Logging in, Usernames/passwords, Realms (Native/LDAP/AD/SAML/PKI/etc) Team:Security Meta label for security team
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants