node-auth0
Node.js client library for the Auth0 platform.
Installation
npm install auth0
Authentication API Client
This client must be used to access Auth0's Authentication API.
The AuthenticationClient constructor takes an optional client ID, if specified it will be used as default value for all endpoints that accept a client ID.
var AuthenticationClient = require('auth0').AuthenticationClient;
var auth0 = new AuthenticationClient({
domain: '{YOUR_ACCOUNT}.auth0.com',
clientId: '{OPTIONAL_CLIENT_ID}'
});
Management API Client
The Auth0 Management API is meant to be used by back-end servers or trusted parties performing administrative tasks. Generally speaking, anything that can be done through the Auth0 dashboard (and more) can also be done through this API.
Initialize your client class with an API v2 token and a domain.
var ManagementClient = require('auth0').ManagementClient;
var management = new ManagementClient({
token: '{YOUR_API_V2_TOKEN}',
domain: '{YOUR_ACCOUNT}.auth0.com'
});
Note: When using at browser you should use
telemetry: false
.
To obtain automatically a Management API token via the ManagementClient, you can specify the parameters clientId
, clientSecret
(use a Non Interactive Client) and optionally scope
.
Behind the scenes the Client Credentials Grant is used to obtain the access_token
and is by default cached for the duration of the returned expires_in
value.
var ManagementClient = require('auth0').ManagementClient;
var auth0 = new ManagementClient({
domain: '{YOUR_ACCOUNT}.auth0.com',
clientId: '{YOUR_NON_INTERACTIVE_CLIENT_ID}',
clientSecret: '{YOUR_NON_INTERACTIVE_CLIENT_SECRET}',
scope: "read:users write:users",
});
Make sure your ClientId is allowed to request tokens from Management API in Auth0 Dashboard
To obtain a Management API token from your node backend, you can use Client Credentials Grant using your registered Auth0 Non Interactive Clients
var AuthenticationClient = require('auth0').AuthenticationClient;
var auth0 = new AuthenticationClient({
domain: '{YOUR_ACCOUNT}.auth0.com',
clientId: '{CLIENT_ID}',
clientSecret: '{CLIENT_SECRET}'
});
auth0.clientCredentialsGrant({
audience: 'https://{YOUR_ACCOUNT}.auth0.com/api/v2/',
scope: '{MANAGEMENT_API_SCOPES}'
}, function (err, response) {
if (err) {
// Handle error.
}
console.log(response.access_token);
});
Also you can request a token when the user authenticates using any of our client side SDKs, e.g. auth0.js.
Promises and callbacks
Be aware that all methods can be used with promises or callbacks. However, when a callback is provided no promise will be returned.
// Using callbacks.
management.getUsers(function (err, users) {
if (err) {
// handle error.
}
console.log(users);
});
// Using promises.
management
.getUsers()
.then(function (users) {
console.log(users);
})
.catch(function (err) {
// Handle error.
});
Documentation
You can find this library documentation in this page.
For more information about auth0 check our documentation page.
What is Auth0?
Auth0 helps you to:
- Add authentication with multiple authentication sources, either social like Google, Facebook, Microsoft Account, LinkedIn, GitHub, Twitter, Box, Salesforce, amont others, or enterprise identity systems like Windows Azure AD, Google Apps, Active Directory, ADFS or any SAML Identity Provider.
- Add authentication through more traditional username/password databases.
- Add support for linking different user accounts with the same user.
- Support for generating signed Json Web Tokens to call your APIs and flow the user identity securely.
- Analytics of how, when and where users are logging in.
- Pull data from other sources and add it to the user profile, through JavaScript rules.
Create a free Auth0 Account
- Go to Auth0 and click "Try Auth0 for Free".
- Use Google, GitHub or Microsoft Account to login.
Issue Reporting
If you have found a bug or if you have a feature request, please report them at this repository issues section. Please do not report security vulnerabilities on the public GitHub issue tracker. The Responsible Disclosure Program details the procedure for disclosing security issues.
Author
License
This project is licensed under the MIT license. See the LICENSE file for more info.