Rafael Pettersen Comments - Answer Overflow

Rafael Pettersen

Posts Comments

WWasp

•Created by Rafael Pettersen on 12/31/2024 in #🙋questions

AuthUser in Server

@kapa.ai there is no getToken from Wasp

36 replies

WWasp

•Created by Rafael Pettersen on 12/31/2024 in #🙋questions

AuthUser in Server

@kapa.ai that did not work, how can i pass the wasp user authorization to the headers, for instance, to be used in useChat?

36 replies

WWasp

•Created by Rafael Pettersen on 12/31/2024 in #🙋questions

AuthUser in Server

@kapa.ai i'm calling the api from a external module:

import { useChat } from 'ai/react'

import { useChat } from 'ai/react'

and would like the pass header auth like below, is that correct?

headers: {
      Authorization: `Bearer ${localStorage.getItem('token')}`
    }

headers: {
      Authorization: `Bearer ${localStorage.getItem('token')}`
    }

36 replies

WWasp

•Created by Rafael Pettersen on 12/31/2024 in #🙋questions

AuthUser in Server

@kapa.ai on your point 1, how can i sen the authentication token correctly?

36 replies

WWasp

•Created by Rafael Pettersen on 12/31/2024 in #🙋questions

AuthUser in Server

@kapa.ai ok, it kind of worked, i do get context.entities, but context.user is null, even having a user logged in. here's main.wasp:

app.api('chat', {
  fn: { import: 'chatHandler', from: '@src/server/chat' },
  entities: ['Chat'],
  auth: true,
  httpRoute: ['POST', '/api/chat']
});

app.api('chat', {
  fn: { import: 'chatHandler', from: '@src/server/chat' },
  entities: ['Chat'],
  auth: true,
  httpRoute: ['POST', '/api/chat']
});

and here is the api declaration:

export const chatHandler: Chat = async (req, res, context) => {

export const chatHandler: Chat = async (req, res, context) => {

36 replies

WWasp

•Created by Rafael Pettersen on 12/31/2024 in #🙋questions

AuthUser in Server

@kapa.ai and how do i have access to the context? I'm trying to access user data from an api route function, that is declared like this: app.api('chat', { fn: { import: 'handler', from: '@src/server/handler }, auth: true, httpRoute: ['POST', '/api/handler'] });

36 replies

WWasp

•Created by Rafael Pettersen on 12/2/2024 in #🙋questions

Inviting Users

Thanks @Filip, appreciate the heads up. I did manage to work removing

setSession(sessionId)

setSession(sessionId)

and just using

await login({email, password});

await login({email, password});

Is that part of the custom signup action? If not, no problem, will do the extra redundant login once we update the version.

29 replies

WWasp

•Created by Rafael Pettersen on 12/2/2024 in #🙋questions

Inviting Users

Found a solution, here's what it worked for me:

import { setSessionId } from 'wasp/client/api'
import { login } from 'wasp/client/auth'

if (response.sessionId) {
        setSessionId(response.sessionId);
        await login({ email, password });
      }

import { setSessionId } from 'wasp/client/api'
import { login } from 'wasp/client/auth'

if (response.sessionId) {
        setSessionId(response.sessionId);
        await login({ email, password });
      }

29 replies

WWasp

•Created by Rafael Pettersen on 12/2/2024 in #🙋questions

Inviting Users

@kapa.ai If I set the session id using setSessionId(response.sessionId); is it enough to make sure the user is authenticated?

29 replies

WWasp

•Created by Rafael Pettersen on 12/2/2024 in #🙋questions

Inviting Users

@kapa.ai I'm doing the "Custom Signup Logic". Here is the code for the authentication:

const user = await context.entities.User.findFirst({
    where: {
      email,
      tokens: {
        some: {
          value: token,
          expiration_date: {
            gt: new Date()
          }
        }
      }
    },
    include: {
      tokens: true,
      auth: true
    }
  });

  if (!user) {
    throw new HttpError(400, 'Invalid or expired invitation token');
  }
  console.log('user', user);

  // Update user with new credentials
  const providerData = await sanitizeAndSerializeProviderData({
    hashedPassword: password,
    isEmailVerified: true
  });

  const updatedUser = await context.entities.User.update({
    where: { id: user.id },
    data: {
      auth: {
        create: {
          identities: {
            create: {
              providerName: 'email',
              providerUserId: email,
              providerData
            }
          }
        }
      },
      tokens: {
        deleteMany: {} // Remove the invitation token
      }
    },
    include: {
      auth: true
    }
  });
  if (!updatedUser.auth) {
    throw new HttpError(500, 'Failed to create auth record');
  }
  console.log('updatedUser.auth', updatedUser.auth);
  const session = await createSession(updatedUser.auth.id);

  return {
    sessionId: session.id,
    redirectTo: '/app/dashboard'
  };

const user = await context.entities.User.findFirst({
    where: {
      email,
      tokens: {
        some: {
          value: token,
          expiration_date: {
            gt: new Date()
          }
        }
      }
    },
    include: {
      tokens: true,
      auth: true
    }
  });

  if (!user) {
    throw new HttpError(400, 'Invalid or expired invitation token');
  }
  console.log('user', user);

  // Update user with new credentials
  const providerData = await sanitizeAndSerializeProviderData({
    hashedPassword: password,
    isEmailVerified: true
  });

  const updatedUser = await context.entities.User.update({
    where: { id: user.id },
    data: {
      auth: {
        create: {
          identities: {
            create: {
              providerName: 'email',
              providerUserId: email,
              providerData
            }
          }
        }
      },
      tokens: {
        deleteMany: {} // Remove the invitation token
      }
    },
    include: {
      auth: true
    }
  });
  if (!updatedUser.auth) {
    throw new HttpError(500, 'Failed to create auth record');
  }
  console.log('updatedUser.auth', updatedUser.auth);
  const session = await createSession(updatedUser.auth.id);

  return {
    sessionId: session.id,
    redirectTo: '/app/dashboard'
  };

Does it look ok?

29 replies

WWasp

•Created by Rafael Pettersen on 12/2/2024 in #🙋questions

Inviting Users

@kapa.ai related to this issue, i have followed the tutorial https://wasp-lang.dev/docs/auth/entities#custom-signup-action and it is working ok, but considering the user that received a email invite, and after this user first sign in, the authIdentity was set and session created, but why this user still are redirected to the login page, and even if I manually change the url to a internal dashboard, it still requires the user to login?

29 replies

WWasp

•Created by Rafael Pettersen on 12/2/2024 in #🙋questions

Inviting Users

Thanks @kapa.ai, I wil try that approach.

29 replies

Gaming

Programming