Jaeger UI is throwing error when RBAC security plugin is enabled on Opensearch #5958
Replies: 2 comments 3 replies
-
Hey there, @Sidhartha-Biswal! I'm here to help you with your tech questions and bug squashing 🤖 I found a similar open issue and discussion that might be relevant to your problem:
Regarding your specific question about Jaeger supporting the RBAC security plugin for OpenSearch, I wasn't able to find a definitive answer in the repository. However, there are some general troubleshooting steps you can follow for diagnosing "Internal server error" in Jaeger Query logs:
Additionally, the Jaeger UI has specific error handling mechanisms for dealing with HTTP 400 errors from Elasticsearch/OpenSearch. The For more detailed error handling, the Jaeger backend processes and extracts detailed error information from HTTP responses, ensuring meaningful error messages are available for debugging and logging purposes [7][8]. If you haven't already, you might want to check if there are any specific environment variables or flags that need to be set in Jaeger to work with OpenSearch's RBAC security plugin. Unfortunately, I couldn't find specific information on this within the repository. |
Beta Was this translation helpful? Give feedback.
-
RBAC is authorization method, Jaeger only provides authentication via basic auth, token, or mTLS. |
Beta Was this translation helpful? Give feedback.
-
Hi,
We are getting the below error when trying to access Jaeger UI after RBAC security plugin is enabled on Opensearch.
Also, it shows "Internal server error" in the Jaeger Query logs. We are getting the exception as below. Could you please provide more explanation about this exception?
Please find the below screenshot.
Does Jaeger support this RBAC security plugin?
Beta Was this translation helpful? Give feedback.
All reactions