Constructing an RPC server with different authentication requirements for endpoints
How can I construct an RPC server that has different auth requirements for some of the endpoints? For example I have
where endpoints in api require just an api token, auth should be called with an anon key, and rpc should be called with a valid signed JWT. When building the server I'm not sure which combinators to use to handle this.
How do I modify the server behavior for nested RPC schema endpoints to handle this?
where endpoints in api require just an api token, auth should be called with an anon key, and rpc should be called with a valid signed JWT. When building the server I'm not sure which combinators to use to handle this.
How do I modify the server behavior for nested RPC schema endpoints to handle this?
