Status of JWT-based routing?

I found an older thread at https://groups.google.com/forum/#!topic/istio-users/zKyWBkhlJps that mentioned the idea of routing requests based on attributes in a JWT (indepent from using JWTs for authorization/authentication). Is this work planned or in progress anywhere? My use case involves different types of clients declaring their types in JWTs that I issue to them, and then routing client traffic differently based on their type.

If I wanted to do this today, it looks like I would need to route requests to my own proxy that parsed the JWT and added fields to headers that I could then route based on.

3 Likes

Hi @ekuefler I came here looking for the same. So far I have an approach similar to https://github.com/istio/istio/issues/8619 and https://github.com/BarDweller/istio-content-based-routing, but I read filters should not be used for this purpose, especially not with all that logic to read JWT.

I am also trying to remove some of that logic in favour of [Question] Decode JWT and put "sub" into a request header