@gen3labs/futurepass-auth

Community fork of @futureverse/auth (v5.0.3). Same OIDC client surface.

Community fork (gen3labs)

Published under @gen3labs by markibanez as a post-Futureverse-winddown community continuation. Backed by the gen3labs-operated issuer at futurepass.gen3labs.tech and signer at fpsigner.gen3labs.tech. Surface area mirrors the upstream @futureverse/* package one-for-one — switch the import path; the code shape is the same. Register OAuth2 clients at https://futurepass.gen3labs.tech/manageclients.

Version

5.0.3

Published

2026-04-28

License

n/a

Status

fork-active

npm

https://www.npmjs.com/package/@gen3labs/futurepass-auth

Types

./index.d.ts

Maintainers

markibanez

Depends on

oidc-client-ts · cookie-storage · @gen3labs/futurepass-auth-core

Recent versions

5.0.3

## Technical notes

Why use it

You want a maintained alternative to @futureverse/auth after fv winddown.

When to skip it

You still pin to fv-published versions for legacy reasons.

Pairs with

• @gen3labs/futurepass-auth-react — React provider

Alternatives

• @futureverse/auth (fv-winddown) — the upstream

Gotchas

• Forked April 2026. Surface mirrors upstream — switch the import path.

Upstream README

Futureverse Auth

Provides an Open ID Connect Authentication library for FuturePass.

Installation

npm:

    npm install @futureverse/auth --save

yarn:

    yarn add @futureverse/auth

pnpm:

    pnpm add @futureverse/auth

bun:

    bun add @futureverse/auth

Register your client

First, you will need to register an OAuth2 client with the Pass Online Identity Provider using the Manage Clients Console:

• Gen3: https://futurepass.gen3labs.tech/manageclients

Usage

PKCE Auth Client Setup

Use the same client ID and redirect URI for the environment you configured your client in.

import { FutureverseAuthClient } from '@futureverse/auth';

const authClient = new FutureverseAuthClient({
  clientId: '<your-client-id>',
  environment: 'production',
  redirectUri: '<your-redirect-uri>',
  postLogoutRedirectUri: '<your-post-logout-redirect-uri>',
});

Sign in

For Web3 wallet authentication, a signer interface is required. The user needs to sign a message so the identity service can verify their identity.

Signer adapters are available from the Signer SDK.

For custodial authentication, set type as email, facebook, google, tiktok or x.

import { EthereumSigner } from '@futureverse/signer';
...
// Sign in custodial options with popup
const type = 'eoa' // 'eoa' is for web3 wallet sign in
const address = '<selected-web3-wallet-address>';
const signer: Signer = new EthereumSigner(...);

await authClient.signInPass({
    type, // eoa | email | facebook | google | tiktok | x
    address,
    state,
    signer,
    authFlow, //'popup' | 'redirect' | 'silent' 
    responseMode, //'query' | 'fragment' | 'form_post' | 'web_message'
});

Handle Redirect

Once the user has signed in, they will be redirected to the redirect URI that was set up in the client. This step is required for the user session to be updated and any open sign in popups to close automatically.

...
await authClient.verifyAndLoadUser();

Getting the user

This method can return the current user if signed in.

...
await authClient.getUser();

Sessions

The session object contains the user object as well as the FuturePass address and EOA address.

...
const session = authClient.userSession;
const futurepassAddress = session.futurepass;
const eoaAddress = session.eoa;
const user = session.user;

Sign out

...
await authClient.signOutPass({ 
    flow: 'redirect', // redirect | silent
    postRedirecturi: '<post_logout_redirect_uri>' // optional
    disableConsent: false // "true" by default
});

Source: https://www.npmjs.com/package/@gen3labs/futurepass-auth · captured 2026-05-02