You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the solution you'd like
I have a Keycloak authentication service running in my K8s cluster and would like to use that to authenticate fission calls
Describe alternatives you've considered
It might be possible to use some middleware to make Fission work with Keycloak
Additional context
I'm also using Traefik as ingress controller. My other services that run on my K8s cluster are secured using mesosphere/traefik-forward-auth. That works like a charm. But that's for websites with a frontend where users can log in. That wouldn't work for RESTful APIs where no human user can user enter credentials.
The text was updated successfully, but these errors were encountered:
@HWiese1980 If you are already using traefix ingress and auth you can just route traffic from router via traffic ingress and use auth you are already using.
Other way is using any oauth2-proxy which sits in front of fission router.
As of now Fission router supports basic auth, we may extend it to support for consuming OIDC provider in future. But I don't think we can do beyond that.
Describe the solution you'd like
I have a Keycloak authentication service running in my K8s cluster and would like to use that to authenticate fission calls
Describe alternatives you've considered
It might be possible to use some middleware to make Fission work with Keycloak
Additional context
I'm also using Traefik as ingress controller. My other services that run on my K8s cluster are secured using mesosphere/traefik-forward-auth. That works like a charm. But that's for websites with a frontend where users can log in. That wouldn't work for RESTful APIs where no human user can user enter credentials.
The text was updated successfully, but these errors were encountered: