26 replies

Seeking Guidance on Handling Authentication with SignUp & SignIn RPC Effects

Hey all! I would love some guidance/recommendation on how to achieve the following:

SignUp & SignIn RPC effects: How do you recommend handling auth? I am currently using NextJS server actions, setting a session cookie, and in my TRPC router middleware grabbing the session & setting a "User" object in the request context.

I am not tied to using this implementation!

// My TRPC middleware that creates the context
export const createTRPCContext = async (opts: { headers: Headers }) => {
  // validates cookie & session, returns `user`: { id, name, etc... } object
  const { session, user } = await uncachedValidateRequest();

  return {
    session,
    user,
    db,
    headers: opts.headers,
  };
};

// My TRPC middleware that creates the context
export const createTRPCContext = async (opts: { headers: Headers }) => {
  // validates cookie & session, returns `user`: { id, name, etc... } object
  const { session, user } = await uncachedValidateRequest();

  return {
    session,
    user,
    db,
    headers: opts.headers,
  };
};

A follow up question to this:
- How have you handled unauthenticated vs authenticated RPC effects? Should I handle this check inside the RPC effect & throw an "Unauthenticated" error?

Effect Community•16mo ago•

26 replies

James!

Seeking Guidance on Handling Authentication with SignUp & SignIn RPC Effects

I am not tied to using this implementation!

// My TRPC middleware that creates the context
export const createTRPCContext = async (opts: { headers: Headers }) => {
  // validates cookie & session, returns `user`: { id, name, etc... } object
  const { session, user } = await uncachedValidateRequest();

  return {
    session,
    user,
    db,
    headers: opts.headers,
  };
};

// My TRPC middleware that creates the context
export const createTRPCContext = async (opts: { headers: Headers }) => {
  // validates cookie & session, returns `user`: { id, name, etc... } object
  const { session, user } = await uncachedValidateRequest();

  return {
    session,
    user,
    db,
    headers: opts.headers,
  };
};

A follow up question to this:
- How have you handled unauthenticated vs authenticated RPC effects? Should I handle this check inside the RPC effect & throw an "Unauthenticated" error?

Seeking Guidance on Handling Authentication with SignUp & SignIn RPC Effects

Similar Threads

Seeking Guidance on Handling Authentication with SignUp & SignIn RPC Effects

Similar Threads

Similar Threads

Similar Threads