-
Notifications
You must be signed in to change notification settings - Fork 282
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
Replace uses of deprecated TransportClient #1578
Labels
Comments
19 tasks
This was referenced Mar 2, 2022
jochenkressin
added a commit
to jochenkressin/security
that referenced
this issue
Mar 23, 2022
…1578) Signed-off-by: Jochen Kressin <[email protected]>
jochenkressin
added a commit
to jochenkressin/security
that referenced
this issue
Mar 23, 2022
Signed-off-by: Jochen Kressin <[email protected]>
3 tasks
peternied
pushed a commit
to peternied/security
that referenced
this issue
Apr 7, 2022
…1578) Signed-off-by: Jochen Kressin <[email protected]>
peternied
pushed a commit
to peternied/security
that referenced
this issue
Apr 7, 2022
Signed-off-by: Jochen Kressin <[email protected]>
jochenkressin
added a commit
to jochenkressin/security
that referenced
this issue
Apr 10, 2022
) While we do not need any transport client auth/auth code anymore, we still need to check the privileges of an injected user on transport layer. This functionality was removed by mistake and is reenabled by this commit. Signed-off-by: Jochen Kressin <[email protected]>
davidlago
pushed a commit
that referenced
this issue
Apr 12, 2022
* Remove code related to TransportClient auth/auth (#1578) Signed-off-by: Jochen Kressin <[email protected]>
wuychn
pushed a commit
to ochprince/security
that referenced
this issue
Mar 16, 2023
* Remove code related to TransportClient auth/auth (opensearch-project#1578) Signed-off-by: Jochen Kressin <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
After the deprecated
TransportClient
was removed in2.0
, we need to go through the uses in this repo and update the to use a REST client instead.Current behavior
Building the security plugin against OpenSearch 2.0 gives the following error:
Acceptance criteria
Security plugin builds against OpenSearch 2.0 with no errors, test pass.
The text was updated successfully, but these errors were encountered: