The Openfort js library provides convenient access to handle client session keys and return signed messages back to Openfort from applications written in client-side JavaScript.
npm install @openfort/openfort-js
yarn add @openfort/openfort-js
With the Openfort Unity SDK, you can sign transaction intents using one of four methods or signers:
const sdk = new Openfort({ baseConfiguration: { publishableKey: "pk_test_XXXXXXX"} });
The Session Signer allows you to use external signing keys, without needing to provide it every time. Here's how to use it:
configureSessionKey()
. This method returns an Ethereum address and a boolean indicating whether you need to register the key from the backend.const sessionKey = sdk.configureSessionKey();
sessionKey.isRegistered
boolean is false, register the key from the backend. Refer to the documentation for session management.This method allows you to externally sign transaction intents without logging in or additional configurations:
const response = await sdk.sendSignatureTransactionIntentRequest("tin_xxxx", '0xUserOperationHash');
The Embedded Signer uses SSS to manage the private key on the client side. To learn more, visit our security documentation.
LoginWithEmailPassword
, AuthenticateWithOAuth
or if not registred SignUpWithEmailPassword
. Then call ConfigureEmbeddedSigner
. const shieldAuth: ShieldAuthentication = {
auth: ShieldAuthType.OPENFORT,
token: identityToken,
authProvider: "firebase",
tokenType: "idToken",
};
await sdk.loginWithEmailPassword("email", "password");
// using automatic recovery
await sdk.configureEmbeddedSigner(chainId, shieldAuth);
For now the only two recovery method available are the PasswordRecovery
and AutomaticRecovery
. Learn more about the recovery methods.
const response = await sdk.sendSignatureTransactionIntentRequest("transactionIntentId", "userOp");
Generated using TypeDoc