yes. Here are my commands list starting from cockroach commands.

But for spicedb migrate i did not use any grpc_shared_key param

cockroach start --insecure --store=node1 --listen-addr=localhost:26257 --http-addr=localhost:8080 --join=localhost:26257,localhost:26258,localhost:26259 --background cockroach start \ --insecure \ --store=node2 \ --listen-addr=localhost:26258 \ --http-addr=localhost:8081 \ --join=localhost:26257,localhost:26258,localhost:26259 \ --background cockroach start --insecure --store=node3 --listen-addr=localhost:26259 --http-addr=localhost:8082 --join=localhost:26257,localhost:26258,localhost:26259 --background cockroach init --insecure --host=localhost:26257 grep 'node starting' node1/logs/cockroach.log -A 11 spicedb migrate head --datastore-engine cockroachdb --datastore-conn-uri="postgresql://localhost:26257/defaultdb?sslmode=disable&user=root"

spicedb serve --grpc-preshared-key “somerandomkeyhere” --datastore-engine=cockroachdb --datastore-conn-uri="postgres://root@localhost:26257/defaultdb?sslmode=disable"

why did you have to change the format of the datastore URI?

I don't think that

postgresql://

should work, are you sure your migrate actually succeeded?

yes, it actually did

the version that was present in the documents was giving me connection refused error

cockroach db after spicedb migration.

are you running over any kind of load balancer, service mesh, or sdn?

none, it's just a local cluster

i mean between spicedb and zed

but for spicedb migrate - do we have to use the shared key?

nope.

no, the shared key is just for securing traffic between spicedb and clients

what versions of spicedb and zed are you using? i'll try to repro tomorrow morning

spicedb - v1.10.0 zed -0.4.4

thank you.

also the issue is just not with the zed client - i tried the python version too and found the same issue -

@Rupa you're using a token from Authzed.com, but trying to hit your local SpiceDB

I deleted your message because it contained your token; I recommend deleting the token as well

Hi @Joey I actually used multiple versions of the key starting from "somerandomkey", "secrettoken" and the one defined on authzed.com too. I have the invalid token issue first and after I set the context, I now face protocol issues.

protocol issues from

zed

?

yep. But now despite setting the context - I get permission denied - invalid preshared key, invalid pre shared token;

9:36PM INF started call grpc.code=OK grpc.component=server grpc.method=WriteRelationships grpc.method_type=unary grpc.service=authzed.api.v1.PermissionsService grpc.start_time=2022-08-04T21:36:25-07:00 grpc.time_ms=0.01 peer.address=127.0.0.1:50478 protocol=grpc requestID=deab8b00530fab06753294984316f268 9:36PM WRN finished call grpc.code=PermissionDenied grpc.component=server grpc.error="rpc error: code = PermissionDenied desc = invalid preshared key: invalid token" grpc.method=WriteRelationships grpc.method_type=unary grpc.service=authzed.api.v1.PermissionsService grpc.start_time=2022-08-04T21:36:25-07:00 grpc.time_ms=0.065 peer.address=127.0.0.1:50478 protocol=grpc requestID=deab8b00530fab06753294984316f26

what does

zed context list

show?

Also another question - cockroach provides the metric data authomatically at localhost:8080 but since spice db is running at the same port - i'm missing out on the data - is there any other dashboard that i can use?