Skip to content

Conversation

@slobodanadamovic
Copy link
Contributor

Extending extractCredentials method to accept ThreadContext
in order to allow associating any additional request headers with
the authentication token.

Extending `extractCredentials` method to accept `ThreadContext` in order
to allow associating any additional request headers with the authentication
token.
@slobodanadamovic slobodanadamovic self-assigned this Jul 3, 2025
@elasticsearchmachine elasticsearchmachine added v9.2.0 serverless-linked Added by automation, don't add manually labels Jul 3, 2025
@slobodanadamovic slobodanadamovic added >non-issue :Security/Authentication Logging in, Usernames/passwords, Realms (Native/LDAP/AD/SAML/PKI/etc) Team:Security Meta label for security team labels Jul 4, 2025
@slobodanadamovic slobodanadamovic marked this pull request as ready for review July 4, 2025 06:37
@elasticsearchmachine
Copy link
Collaborator

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

@slobodanadamovic
Copy link
Contributor Author

After brief discussion with @n1v0lg , we don't actually need this change and can solve it by passing the ThreadPoll (ThreadContext) to the authenticator service. Hence I will close this PR.

@slobodanadamovic slobodanadamovic removed the serverless-linked Added by automation, don't add manually label Jul 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

>non-issue :Security/Authentication Logging in, Usernames/passwords, Realms (Native/LDAP/AD/SAML/PKI/etc) Team:Security Meta label for security team v9.2.0

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants