The goal is to reference AuthConfig CRs by labels, on routes.
Ideally, the user could build the k8s labels or the name of the AC dynamically, based on the request headers / transformations (subject to sanitization, of course).
We had this question from a prospect, managing multiple tenants on his IoT platform.
This issue has been marked as stale because of no activity in the last 180 days. It will be closed in the next 180 days unless it is tagged "no stalebot" or other activity occurs.
The goal is to reference AuthConfig CRs by labels, on routes.
Ideally, the user could build the k8s labels or the name of the AC dynamically, based on the request headers / transformations (subject to sanitization, of course).
We had this question from a prospect, managing multiple tenants on his IoT platform.
A similar feature request exists for RLCs: https://github.com/solo-io/gloo/issues/4115