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

external authorization sample #4354

Closed
tirelibirefe opened this issue Feb 20, 2022 · 3 comments
Closed

external authorization sample #4354

tirelibirefe opened this issue Feb 20, 2022 · 3 comments
Labels
kind/question Categorizes an issue as a user question. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@tirelibirefe
Copy link

Hello,
I need to an authorization system integration for custom developed apis and some other applications like Prometheus which needs to be protected.

I've seen external authorization configuration for contour-authserver. I looked for another external authorization configuration sample but couldn't have found.

What is the correct walk-through for that? Is there any sample configuration which is used Keycloak, Microsoft/Azure LDAP or anything else as external auth server?

Thanks & Regards

@OrlinVasilev OrlinVasilev added the kind/question Categorizes an issue as a user question. label Feb 22, 2022
@youngnick
Copy link
Member

So sorry to take a long time to get back to you here @tirelibirefe. We don't currently have a good example of using contour-authserver for Oauth flows, although we did merge support for it earlier. Sorry.

I'm also working on a way to do Oauth using Envoy's inbuilt filter in #2664, which would mean that you can do some oauth flows without needing the external auth service.

@github-actions
Copy link

github-actions bot commented Nov 6, 2022

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 Nov 6, 2022
@github-actions
Copy link

github-actions bot commented Dec 7, 2022

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 Dec 7, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/question Categorizes an issue as a user question. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Development

No branches or pull requests

3 participants