Creates a UserSession object
Decrypts data encrypted with encryptContent
with the
transit private key.
encrypted content.
Optional
options: { Optional
privateThe hex string of the ECDSA private key to use for decryption. If not provided, will use user's appPrivateKey.
decrypted content.
Encrypts the data provided with the app public key.
the data to encrypt
Optional
options: EncryptContentOptionsStringified ciphertext object
Try to process any pending sign in request by returning a Promise
that resolves
to the user data object if the sign in succeeds.
the signed authentication response token
that resolves to the user data object if successful and rejects if handling the sign in request fails or there was no pending sign in request.
Rest
...args: [transitKey?: string, redirectURI?: string, manifestURI?: string, scopes?: string[], appDomain?: string, expiresAt: number, extraParams: any]makeAuthRequest was renamed to makeAuthRequestToken
Generates an authentication request that can be sent to the Blockstack browser for the user to approve sign in. This authentication request can then be used for sign in by passing it to the [[redirectToSignInWithAuthRequest]] method.
Note: This method should only be used if you want to use a customized authentication flow. Typically, you'd use [[redirectToSignIn]] which is the default sign in method.
Optional
transitKey: stringA HEX encoded transit private key.
Optional
redirectURI: stringLocation to redirect the user to after sign in approval.
Optional
manifestURI: stringLocation of this app's manifest file.
Optional
scopes: string[]The permissions this app is requesting. The default is store_write
.
Optional
appDomain: stringThe origin of the app.
The time at which this request is no longer valid.
Any extra parameters to pass to the authenticator. Use this to pass options that aren't part of the Blockstack authentication specification, but might be supported by special authenticators.
the authentication request token
Generated using TypeDoc
Represents an instance of a signed in user for a particular app.
A signed in user has access to two major pieces of information about the user, the user's private key for that app and the location of the user's gaia storage bucket for the app.
A user can be signed in either directly through the interactive sign in process or by directly providing the app private key.