---------------------- If you're using Wasp's built-in authentication, you should know that Wasp has moved from using JWT tokens to using sessions for authentication. This is an important distinction that affects how you would access authentication information. ## Current Authentication System in Wasp Wasp now uses sessions rather than JWT tokens for authentication: > Wasp's auth uses sessions to keep track of the logged-in user. The session is stored in `localStorage` on the client and in the database on the server. Under the hood, Wasp uses the excellent [Lucia Auth v3]() library for session management. [Auth Overview - Sessions]() This means that you don't directly access a token as you might expect. Instead, Wasp handles the session management for you behind the scenes. ## Accessing the Authenticated User To access the authenticated user in your client code, you can use the `useAuth` hook: ```javascript import { useAuth, logout } from 'wasp/client/auth' export function MyComponent() { const { data: user } = useAuth() if (!user) { return Not logged in } else { return ( <>

Hello, {user.username}

) } } ``` ## For External Applications If you're trying to access the authentication from an external application (like your previous question suggested), this becomes more complex because Wasp doesn't currently expose a direct API for authenticating users from external applications. As noted in a Discord conversation: > Unfortunately, Wasp doesn't yet expose the API for authenticating users (the idea is to use its internal RPC, which doesn't make sense for your use case). [Discord support thread]()

Call custom api externally

Similar Threads

Similar Threads

Similar Threads