Skip to content
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

Support Jaeger Login/Authentication #211

Closed
aviranco opened this issue May 8, 2018 · 8 comments
Closed

Support Jaeger Login/Authentication #211

aviranco opened this issue May 8, 2018 · 8 comments
Labels

Comments

@aviranco
Copy link

aviranco commented May 8, 2018

I would like to expose the Jaeger UI with user/password authentication, is it currently possible?
If not, I think it would be really useful so only authorized users can view the logs

@yurishkuro
Copy link
Member

it is possible, but it's not a function that Jaeger provides directly. At Uber we run Jaeger UI behind an nginx proxy that is integrated with single sign-on.

@Marusyk
Copy link

Marusyk commented Oct 3, 2019

any plans to add auth for dashboard?

@yurishkuro
Copy link
Member

Please see Issue #1718 for the summary of available security mechanisms in Jaeger.

@a1300
Copy link

a1300 commented Dec 22, 2020

@yurishkuro can you share your nginx revers proxy configuration?
Thanks in advance

@Marusyk
Copy link

Marusyk commented Dec 22, 2020

Hi @a1300, I can share mine if it helps

I have simple basic auth here

apiVersion: v1
kind: Secret
metadata:
  name: basic-auth
type: Opaque
data:
  auth: ZWxhc3RpYzokYXByMSRCMDVsdW1FbSRWNWJkMmVqWE02RXBQVFZWVnVnbE8v
---

apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  name: jaeger-ingress
  annotations:
    kubernetes.io/ingress.class: nginx
    certmanager.k8s.io/cluster-issuer: letsencrypt-production
    nginx.ingress.kubernetes.io/rewrite-target: /
    nginx.ingress.kubernetes.io/auth-type: basic
    nginx.ingress.kubernetes.io/auth-secret: basic-auth
    nginx.ingress.kubernetes.io/auth-realm: 'Authentication Required - ok'
spec:
  tls:
  - hosts:
    - host.com
    secretName: jaeger-crt
  rules:
  - host: host.com
    http:
      paths:
      - path: /jaeger
        backend:
          serviceName: jaeger
          servicePort: 16686

@yurishkuro
Copy link
Member

@yurishkuro can you share your nginx revers proxy configuration?

I don't have access to it anymore, and it was not specific to Jaeger, but a general single sign-on for all internal web tools.

@ilyakaznacheev
Copy link

Any progress on this topic?

@yurishkuro
Copy link
Member

We have no plans to implement login as a standalone feature, there are many existing solutions for that via reverse proxies. We may revisit if/when we support multi-tenancy and need to implement authorization.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants