New Case Study:See how Anthropic automated 95% of dependency reviews with Socket.Learn More
Socket
Sign inDemoInstall
Socket

@futureverse/auth

Package Overview
Dependencies
Maintainers
17
Versions
65
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

@futureverse/auth

Provides an Open ID Connect Authentication library for FuturePass.

  • 4.1.1
  • latest
  • npm
  • Socket score

Version published
Weekly downloads
0
decreased by-100%
Maintainers
17
Weekly downloads
 
Created
Source

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:

  • Production: https://login.pass.online/manageclients
  • Development / Staging: https://login.passonline.cloud/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
});

FAQs

Package last updated on 29 Jan 2025

Did you know?

Socket

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Install

Related posts

SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap
  • Changelog

Packages

npm

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc