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.

Sign up for GitHub

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

Jump to bottom

Support Okta for authentication #4044

Closed
xaleeks opened this issue Sep 20, 2021 · 2 comments
Closed

Support Okta for authentication #4044

xaleeks opened this issue Sep 20, 2021 · 2 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/needs-triage Indicates that an issue needs to be triaged by a project contributor. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. task

Comments

@xaleeks
Copy link

xaleeks commented Sep 20, 2021

This issue is a sub-task of the epic #2664

support authentication with Okta for http/https requests. Contour in this instance should act as a client to relay the request to an OKTA server for authentication before letting the request through to upstream services.

opportunistic: consider implementing this at the virtualhost granularity so different routes can use different auth backends (LDAP, OIDC, managed tokens like Vault), although I don’t think this is P0. Most enterprises use one authN identity provider.
@xaleeks xaleeks added kind/feature Categorizes issue or PR as related to a new feature. lifecycle/needs-triage Indicates that an issue needs to be triaged by a project contributor. task labels Sep 20, 2021
@xaleeks xaleeks changed the title support Okta for authentication Support Okta for authentication Sep 20, 2021
@youngnick youngnick mentioned this issue Nov 2, 2021
Open
@github-actions
Copy link

The Contour project currently lacks enough contributors to adequately respond to all Issues.

This bot triages Issues according to the following rules:

  • After 60d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, the Issue is closed

You can:

  • Mark this Issue as fresh by commenting
  • Close this Issue
  • Offer to help out with triage

Please send feedback to the #contour channel in the Kubernetes Slack

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Mar 13, 2023
@github-actions
Copy link

The Contour project currently lacks enough contributors to adequately respond to all Issues.

This bot triages Issues according to the following rules:

  • After 60d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, the Issue is closed

You can:

  • Mark this Issue as fresh by commenting
  • Close this Issue
  • Offer to help out with triage

Please send feedback to the #contour channel in the Kubernetes Slack

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Apr 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/needs-triage Indicates that an issue needs to be triaged by a project contributor. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. task
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@xaleeks