Skip to content
This repository has been archived by the owner on Apr 17, 2019. It is now read-only.

[nginx-ingress-controller] JWT and Client SSL Verify #1327

Closed
dnascimento opened this issue Jul 8, 2016 · 6 comments
Closed

[nginx-ingress-controller] JWT and Client SSL Verify #1327

dnascimento opened this issue Jul 8, 2016 · 6 comments
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.

Comments

@dnascimento
Copy link

NGINX can handle JWT token validation to provide authentication on APIs.
Verify Client SSL Certificate should also be possible.

It requires to change the spec in kubernetes project to add:

 jwt:
    - hosts:
        - XXXXXX
 client-verify:
     - hosts:
         - XXXXX
@aledbf
Copy link
Contributor

aledbf commented Jul 8, 2016

@dnascimento the NGINX ingress controller is just an implementation of Ingress spec.
Please open a proposal in the kubernetes/features repository to add JWT token validation.

@aledbf
Copy link
Contributor

aledbf commented Jul 8, 2016

@dnascimento I forgot to add that we can add this feature just for the nginx ingress controller using 2 annotations

@dnascimento
Copy link
Author

What about the following changes to the spec:

  1. JWT: Per host or per-location
  2. ClientVerify: Per host
  3. TLS as host property too, instead of an array.
  4. Specify ports on hostname.
  5. Support regex on hostname (nginx)
  6. Allow to mount a lua script and exec on host

This is great when combined with ELB! Great job!

@fejta-bot
Copy link

Issues go stale after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

Prevent issues from auto-closing with an /lifecycle frozen comment.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or @fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 16, 2017
@fejta-bot
Copy link

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or @fejta.
/lifecycle rotten
/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Jan 15, 2018
@fejta-bot
Copy link

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.
Projects
None yet
Development

No branches or pull requests

4 participants