Jaeger v2 UI authentication #7124
Replies: 1 comment
-
Jaeger UI does not support any notion of accounts or roles, so there is no need to authenticate users directly within Jaeger UI. To restrict access to Jaeger UI, it is recommended to run a reverse proxy in front of it, such as HAProxy, NGINX, or Keycloak. These proxies support a wide variety of integrations with authentication and single sign-on services. You can refer to the article you mentioned for an example of protecting Jaeger UI with Keycloak, as the approach is applicable to both v1 and v2 [1][2]. To continue talking to Dosu, mention @dosu. Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi team,
Is there a way to authenticate the user for the Jaeger UI on the v2? I found an article explaining the sidecar proxy with Jaeger query. But that is for V1 where the components are deployed independently.
Beta Was this translation helpful? Give feedback.
All reactions