or have Next.js check the permissions directly in

getServerSideProps

I have a working test that does the latter

if possible could you share the Next.js server side rendering example?

that would be of great help

it depends on what you're using for authn; do you have a preferred authn provider?

We're using Ory's kratos for authn and also using Ory's Oathkeeper as an Access Control Decision API

ok

so in my prototype, you can do:

the

withCapabilities

takes one (or more) permissions to check, and then places them into the props given to the page

it uses the authzed-node client library to make the checks

https://github.com/authzed/authzed-node is the client it uses

I'll see if I can post up this prototype code this week

this seems like a viable solution, I'll also wait for the prototype for our reference

thanks for the insight 😄

of course!

if you can provide me guidance on how you're getting the user's ID in next.js from kratos

then I can add support for it into my prototype as well

we're using the library that Ory recommends for Next.js. After a login has been performed, a http-only cookie is set and sent back to the frontend. If the user is logged in then we can extract the session from the cookie which then has the user details

you can refer this for example

perfect; I'll see if I can add that today to my prototype, clean it up a bit, and then post it up on Github this week

you can see it in working on this example deployment they have put up for users to test it out

Hi! 1) SpiceDB is fully open source. We do all development on it in the open and are collaborating with outside organizations and individual contributors. Authzed sells the serverless platform for SpiceDB or an on-premise version of that serverless platform. We want all of the tools that make developers successful at using SpiceDB to be open because it'll drive adoption of our products. SpiceDB is not the product. 2) We typically gauge interest from the community before implementing a new datastore. With proven demand, we will accept a contribution that implements one, so long as we think we can keep it maintained. I created an issue for gauging the interest of YugaByteDB here: https://github.com/authzed/spicedb/issues/427

Thank you very much for the response!

in the protobuf spec for the v1 api the responses for WriteRelationships and DeleteRelationships has the zed token as optional. under what conditions would those operations not return a zed token?

@User in practice: never. they are always returned unless an error occurs, in which case that's an error, instead of a normal response

thank you!