[](https://www.npmjs.com/package/@logto/node) [](https://github.com/logto-io/js/actions/workflows/main.yml) [![Codecov]
npm install @logto/node


The Logto Node.js SDK written in TypeScript.
``bash`
npm install @logto/node
`bash`
yarn add @logto/node
`bash`
pnpm add @logto/node
As the name suggests, Logto Node.js SDK is the foundation of all Logto SDKs that run in Node.js (Express, Next.js, etc.). @logto/node extends @logto/client and provides a Node.js specific implementation of the client adapters:
- Implements requester by using package node-fetch.generateCodeChallenge
- Implements , generateCodeVerifier, generateState methods by using crypto.
Usually, you are not expected to use it directly in your application, but instead choosing a framework specific SDK that built on top of it. We have already released a set of official SDKs to accelerate your integration. Check this out and get started!
If Logto does not support your traditional web framework and you want to create your own SDK from scratch, we recommend checking out the SDK specification first. You can also refer to our Express SDK and Next.js SDK to learn more about the implementation details.
Prepare your project by installing @logto/node as the dependency.
The store adapter is used to store the Logto session information. In most cases, we recommend using cookie-based storage to store the session information.
`typescript
// storage.ts
import { CookieStorage } from '@logto/node';
export const storage = new CookieStorage({
encryptionKey: '
cookieKey: ,`
isSecure: false, // Set to true if you are using HTTPS
getCookie: (name) => {
// Example usage, get cookie from the request, depends on your framework
return request.cookies[name] ?? '';
},
setCookie: (name, value, options) => {
// Example usage, set cookie to the response, depends on your framework
response.setHeader('Set-Cookie', serialize(name, value, options));
},
});
This will wrap the session data, encrypt it with the encryption key, and store it in the cookie directly.
But the cookie size is limited, so you may need to use external storage like Redis or memory cache to store the session information. Especially when you are using organization features, the session information will be quite large.
`typescript
// storage.ts
import { CookieStorage } from '@logto/node';
class RedisSessionWrapper implements SessionWrapper {
constructor(private readonly redis: Redis) {}
async wrap(data: unknown, _key: string): Promise
const sessionId = randomUUID();
await this.redis.set(logto_session_${sessionId}, JSON.stringify(data));
return sessionId;
}
async unwrap(value: string, _key: string): Promise
if (!value) {
return {};
}
const data = await this.redis.get(logto_session_${value});
return JSON.parse(data);
}
}
export const storage = new CookieStorage({
cookieKey: ,`
sessionWrapper: new RedisSessionWrapper(redis),
isSecure: false, // Set to true if you are using HTTPS
getCookie: (name) => {
// Example usage, get cookie from the request, depends on your framework
return request.cookies[name] ?? '';
},
setCookie: (name, value, options) => {
// Example usage, set cookie to the response, depends on your framework
response.setHeader('Set-Cookie', serialize(name, value, options));
},
});
Continue to prepare the navigation adapter and create the client. You need to implement the "redirect" function to redirect the user to the Logto sign-in page.
`typescript
// client.ts
import { NodeClient } from '@logto/node';
import { config } from './config';
import { storage } from './storage';
export const client = new NodeClient({
...config,
storage,
navigate: (url) => {
// Example usage, navigate to the url, depends on your framework
response.redirect(url);
},
});
`
You can now trigger the sign-in flow by calling the signIn method.
`typescript
// app.ts
import { client } from './client';
await client.signIn({
redirectUri: 'http://localhost:3000/callback',
});
`
You need to handle the sign-in callback by calling the signInCallback method.
`typescript
// app.ts
import { client } from './client';
// You'll need to pass the full url to the callback handler,
// it depends on your framework to get the url.
await client.handleSignInCallback(${request.url});
// After handling the callback, the user is signed in,
// information stored in the storage adapter we created earlier,
// you can now redirect the user to the home page.
response.redirect('/');
`
You can now implement the sign out and other methods by referring to our example implementation in other frameworks.
You can call the getContext method to retrieve the user information and protect your resources based on the context.
`typescript
// app.ts
import { client } from './client';
const { isAuthenticated, claims } = await client.getContext();
if (!isAuthenticated) {
// The user is not signed in, redirect to the sign-in page.
// protect the resource from being accessed by unauthenticated users.
response.redirect('/sign-in');
}
// The user is signed in, you can now do something with the user information.
console.log(claims);
``
We have a list of awesome implementations of Logto SDK:
We are grateful for the amazing Logto community!


