Hey everyone. We are migrating our
# spicedb
h
Hey everyone. We are migrating our serverless set of permission-systems to a self-hosted instance. I'm a little bit confused about providing token for accessing the system and not able to find a fully explanation or example how to do that? I have no problems to do some actions by
zed-cli
and the preshared key. But in our node-app the client (
@authzed/zed-node
) seems to require a token. Passing the pre-shared key throws a
token missing required 'view' permission on the requested permissions system
. What am I missing, where to find help?
y
is this when making queries to serverless or making queries to a self-hosted instance? and is this with spicedb enterprise or open-source spicedb?
h
Is making queries to the self-hosted instance. We are running a spiceDb in a docker image on aws ecs.
(In the serverless version we had the UI to create tokens.)
I'm not sure, if this is the "right" way: https://authzed.com/docs/authzed/concepts/restricted-api-access
y
it is if we're talking about enterprise
it isn't if we're talking about OSS spicedb
h
So adding a config to
spicedb serve
via
—extender-authzed-fgam-endpoint
won't work?
For some reason it now works with the preshared key. I don't get it. (but works now)
y
are we talking about spicedb enterprise?
j
restricted API access is an Enterprise-only feature and is not supported in SpiceDB OSS
6 Views