51–60 of 123 posts
https://istio.io/docs/concepts/network-and-auth/auth.html No option for OAuth2 or JWT? Maybe I'm not understanding the problem Istio solves vs. Envoy
Disclaimer: I work on Istio
There seems to be also other companies involved: Redhat: https://blog.openshift.com/red-hat-istio-launch/ Pivotal: https://content.pivotal.io/blog/pivotal-and-istio-advancing-...
and isn't the entire solution just packaging a proxy developed and open-sourced by Lyft?
https://istio.io/docs/concepts/network-and-auth/auth.html No option for OAuth2 or JWT? Maybe I'm not understanding the problem Istio solves vs. Envoy
Good question. The auth work for this release is mainly focusing on service-to-service authentication. We are looking into adding OAuth2 and JWT support for enduser auth in the future release. Disclaimer: I work on Istio
https://istio.io/docs/concepts/network-and-auth/auth.html No option for OAuth2 or JWT? Maybe I'm not understanding the problem Istio solves vs. Envoy
Good question. The auth work for this release is mainly focusing on service-to-service authentication. We are looking into adding OAuth2 and JWT support for enduser auth in the future release. Disclaimer: I work on Istio
Disclaimer: I work on Istio
Interesting, but there's currently a lot of overlap between competing things that want to inject themselves between service consumers and service producers. There's API gateway products (Apigee, Kong, etc). Load balancers and proxies of various types. Caching and CDN products. More niche stuff like bot blocking, and this attempt to bundle control and statistics. It would be nice if some sort of standard pattern emerg…
Regarding API gateway products, Apigee will actually work with Istio https://apigee.com/about/blog/digital-business/simplifying-m...
Earlier quoted context omitted.
Maybe it depends on the size / complexity of the services. In the 'serverless' trend, such a middleware makes more sense. But essentially, moving too much logic into a middleware may support bad, lazy design decisions that make the middleware a single point of failure - like ESBs.
I'm a big fan of buses or perhaps more accurately I guess semi intelligent pipes with semi intelligent endpoints. I have used RabbitMQ (and Kafka at times) for large portion of my career and anytime I tell people this the bring up the single point of failure. The single point of failure arguments is getting really old and is fairly baseless particularly if your storage (e.g. RDBMS) or network (single zone or even mul…
That sounds like multiple single points of failures, which just means you have more work to do, not that you can throw your hands in the air and say "welp".
Earlier quoted context omitted.
Good question. The auth work for this release is mainly focusing on service-to-service authentication. We are looking into adding OAuth2 and JWT support for enduser auth in the future release. Disclaimer: I work on Istio
Cool. Also - what does Istio use for persistence? I imagine it's gonna persist the data for auth'ing stuff somewhere.
Earlier quoted context omitted.
Good question. The auth work for this release is mainly focusing on service-to-service authentication. We are looking into adding OAuth2 and JWT support for enduser auth in the future release. Disclaimer: I work on Istio
Cool. Also - what does Istio use for persistence? I imagine it's gonna persist the data for auth'ing stuff somewhere.
Disclaimer: I work on Istio