connect()

Othent JS SDK connect() function

Prompts the user to sign in/up (connects the user's wallet) using Auth0's popup.

Note that while connect()'s function signature is identical to that of ArConnect's connect(), you don't need to request permissions from the user to interact with their wallets, as Othent implicitly requires all permissions.

Caution: Users using Othent are giving dApps that use Othent full control of their wallet.

This function will throw an error in the following cases:

  • When passing permissions different to undefined and the default value (all permissions). Passing anything else will throw an error.

  • When this function is called before the user interacts with the page (e.g. by clicking on a button), as that will result in a Unable to open a popup error.

  • When the user closes the Auth0 popup before authenticating, as that will result in a Popup closed error.

  • When authentication fails.

API

connect(
  permissions?: PermissionType[],
  appInfo?: AppInfo,
  gateway?: GatewayConfig,
): Promise<UserDetails | null>;

permissions?: PermissionType[]

An array of permission to request from the user, but only undefined or an array with all permissions are valid. Passing anything else will throw an error.

Caution: Users using Othent are giving dApps that use Othent full control of their wallet.

appInfo?: AppInfo

You must provide your application's name and version, and optionally logo, to the SDK when instantiating it. These values can also be changed when calling connect(), to make Othent compatible with projects using ArConnect.

interface AppInfo {
  /**
   * Name of your app. This will add a tag `App-Name: <appName>` to any transaction signed or sent using `Othent.sign`,
   * `Othent.dispatch` or `Othent.signDataItem`.
   */
  name: string;

  /**
   * Version of your app. This will add a tag `App-Version: <appVersion>` to any transaction signed or sent using
   * `Othent.sign`, `Othent.dispatch` or `Othent.signDataItem`.
   */
  version: string;

  /**
   * Environment your app is currently running on (e.g. "development", "staging", "production", ...). This will add a
   * tag `App-Env: <appEnv>` to any transaction signed or sent using `Othent.sign`, `Othent.dispatch` or
   * `Othent.signDataItem`.
   *
   * If no value (empty `string`) is provided, this will automatically be set to `"development"` if
   * `location.hostname = "localhost"` or `"production"` otherwise.
   */
  env: string;

  /**
   * Image with the logo of your app. Optional and not used for now.
   */
  logo?: UrlString;
}

gateway?: GatewayConfig

If your application requires the usage of a special gateway or you want to test with an ArLocal testnet gateway, you'll have to provide some information about it when connecting to Othent's SDK.

You can set this value when instantiating Othent and also change it when calling connect(), to make Othent compatible with projects using ArConnect.

interface GatewayConfig {
  host: string;
  port: number;
  protocol: "http" | "https";
}

return Promise<UserDetails | null>

A Promise with the UserDetails or null if the log in modal was closed, could not even be opened or authentication failed.

Example usage

import { Othent } from "@othent/kms";

const othent = new Othent({ appInfo, throwErrors: false, ... });

await othent.connect(
  // All permissions are implicit regardless:
  undefined

  // Provide some extra info for our app, if not provided to the constructor:
  {
    name: "Super Cool App",
    version: "1.0.12",
    env: "production",
  },
  
  // Custom gateway, if not provided to the constructor:
  {
    host: "g8way.io",
    port: 443,
    protocol: "https"
  }
);
PreviouscompleteConnectionAfterRedirect()Nextdisconnect()

Last updated