0.1.22 • Published 2 years ago
@elrondnetwork/native-auth v0.1.22
Native Authenticator for JavaScript
Native Authenticator for JavaScript and TypeScript (written in TypeScript).
Distribution
Example
Client-side
const client = new NativeAuthClient();
const init = await client.initialize();
// obtain signature by signing token
const accessToken = client.getToken(address, init, signature);
Client-side config
When initializing the client object, an optional config can also be specified with the following properties:
{
// When used from within a browser, will contain the hostname by default.
// It can be overridden for special situations
// Note: The server-side component will validate the `origin` header, which must
// match with the provided host in the client-side configuration
host: string = 'myApp.com';
// The endpoint from where the current block information will be fetched upon initialization.
// The default value points to the mainnet API, but can be overridden to be network-specific
// or to point to a self-hosted location
apiUrl: string = 'https://api.elrond.com';
// TTL that will be encoded in the access token.
// This value will also be validated by the server and must not be greater than the maximum ttl allowed.
// Default: one day (86400 seconds)
expirySeconds: number = 60 * 60 * 24;
}
Server-side
const server = new NativeAuthServer();
const result = await server.validate(accessToken);
Server-side config
{
// The endpoint from where the current block information will be fetched upon validation.
// The default value points to the mainnet API, but can be overridden to be network-specific
// or to point to a self-hosted location
apiUrl: string = 'https://api.elrond.com';
// An optional list of accepted hosts in case the server component must validate the incoming requests
// by domain
acceptedHosts: string[] = [];
// Maximum allowed TTL from the token.
// Default: one day (86400 seconds)
maxExpirySeconds: number = 86400;
// An optional implementation of the caching interface used for resolving
// latest block timestamp and also to validate and provide a block timestamp given a certain block hash.
// It can be integrated with popular caching mechanisms such as redis
cache?: NativeAuthCacheInterface;
}
0.1.22
2 years ago
0.1.21
2 years ago
0.1.20
2 years ago
0.1.19
2 years ago
0.1.18
2 years ago
0.1.17
2 years ago
0.1.16
2 years ago
0.1.15
2 years ago
0.1.14
2 years ago
0.1.13
2 years ago
0.1.12
2 years ago
0.1.11
2 years ago
0.1.10
2 years ago
0.1.9
2 years ago
0.1.8
2 years ago
0.1.7
2 years ago
0.1.6
2 years ago
0.1.5
2 years ago
0.1.4
2 years ago
0.1.3
2 years ago
0.1.2
2 years ago
0.1.1
2 years ago
0.1.0
2 years ago