Any thoughts on this approach? Or an alternative?
# community
j
Any thoughts on this approach? Or an alternative?
e
With this approach or via the admin API, we highly recommend that you to also use the testing feature before deploying policies
j
Makes sense - is there an alternative to securing the admin API besides basic auth?
e
Currently no. However, what would be your preferred method?
j
Honestly not sure... maybe providing access to a JWT signing secret and allowing valid tokens as an alternative to basic auth
e
ok. We can definitely look into this. If you can think of any better approaches, please let us know.
👍 1
a
I take it you are using database storage for the policy store? If so, I advise against updating the policy store directly as Cerbos also stores metadata in there (versioning etc) along with the actual policies which will get out of sync. What is your reason for considering this route, besides the basic auth point? It's not a model we've considered just yet but open to ideas
j
Mainly that basic auth doesnt' feel production appropriate even for intra-cluster communication
so figured if we're using cerbos for read-only functionality, then we don't need the basic auth...
could handle writes using JWT-authenticated internal service
I think basic JWT token authentication / validation would be better than basic auth... basically I think anything is better than basic auth
I think in general the docs are good, but it would be helpful to have a separate
samples
repo(s) you guys link to that show the full configuration for both sidecar and svc deployment and how that interacts in a cluster... basically best practices fully implemented