@kabeersnetwork/kauth-sdk
v1.0.12
Published
Kabeer Identity Platform SDK, Supports OAuth2 (PKCE, Authorization Code, Client Credintials, Implicit)
Downloads
8
Maintainers
Readme
Kabeer Auth Library: Node.js Client
Currently Incomplete! New Features will be added and server side architecture will be defined.
This is Kabeers Network's officially supported node.js client library for using OAuth 2.0 authorization and authentication with Kabeer's Network APIs.
A comprehensive list of changes in each version may be found in the CHANGELOG.
Table of contents:
Quickstart
Installing the client library
npm install @kabeersnetwork/kauth-sdk
Ways to authenticate
This library provides a variety of ways to authenticate to your Google services.
- OAuth 2 - Use OAuth2 when you need to perform actions on behalf of the end user.
- JSON Web Tokens - Use JWT when you are using a single identity for all users. Especially useful for server->server or server->API communication.
Enable the API you want to use
Before making your API call, you must be sure the API you're calling has been enabled. Go to APIs & Auth > APIs in the Google Developers Console and enable the APIs you'd like to call. For the example below, you must enable the DNS API
.
Supported Node.js Versions
Our client libraries follow the Node.js release schedule. Libraries are compatible with all current active and maintenance versions of Node.js.
Client libraries targeting some end-of-life versions of Node.js are available, and
can be installed via npm dist-tags.
The dist-tags follow the naming convention legacy-(version)
.
Legacy Node.js versions are supported as a best effort:
- Legacy versions will not be tested in continuous integration.
- Some security patches may not be able to be backported.
- Dependencies will not be kept up-to-date, and features will not be backported.
Legacy tags available
legacy-8
: install client libraries from this dist-tag for versions compatible with Node.js 8.
Versioning
This library follows Semantic Versioning.
This library is considered to be General Availability (GA). This means it is stable; the code surface will not change in backwards-incompatible ways unless absolutely necessary (e.g. because of critical security issues) or with an extensive deprecation period. Issues and requests against GA libraries are addressed with the highest priority.
Contributing
Contributions welcome! See the Contributing Guide.
Please note that this README.md
, the samples/README.md
,
and a variety of configuration files in this repository (including .nycrc
and tsconfig.json
)
are generated from a central template. To edit one of these files, make an edit
to its template in this
directory.
License
Apache Version 2.0