node.js based authentication library for Azure with type definitions
Перейти к файлу
Kamil Pajdzik 66697f981f
Fix incorrect path to the main file (#39)
2018-11-19 12:52:36 -08:00
.github Add code owners and issue template (#38) 2018-11-19 11:19:20 -08:00
.vscode Update support for MSI authentication (#13) 2018-09-05 10:44:46 -07:00
lib Rename package to "@azure/ms-rest-nodeauth" (#30) 2018-11-12 13:18:44 -08:00
test Rename package to "@azure/ms-rest-nodeauth" (#30) 2018-11-12 13:18:44 -08:00
.gitattributes initial commit 2017-09-08 11:25:16 -07:00
.gitignore Update package.json and remove package-lock.json 2018-11-14 15:34:42 -08:00
Changelog.md Rename package to "@azure/ms-rest-nodeauth" (#30) 2018-11-12 13:18:44 -08:00
LICENSE Initial commit 2017-09-06 16:29:08 -07:00
README.md Update missing references in samples (#34) 2018-11-13 11:08:20 -08:00
azure-pipelines.yml Add Azure Pipelines configuration (#32) 2018-11-12 13:28:26 -08:00
package.json Fix incorrect path to the main file (#39) 2018-11-19 12:52:36 -08:00
rollup.config.js Add rollup 2018-11-14 15:33:27 -08:00
tsconfig.json Update ms rest (#24) 2018-10-18 15:09:03 -07:00
tslint.json Remove Travis configuration and add no-return-await TS lint rule (#33) 2018-11-12 13:46:57 -08:00

README.md

ms-rest-nodeauth Build Status

This library provides different node.js based authentication mechanisms for services in Azure. It also contains rich type definitions thereby providing good typescrit experience. All the authentication methods support callback as well as promise. IF they are called within an async method in your application then you can use the async/await pattern as well.

Example

username/password based login

import * as msRestNodeAuth from "@azure/ms-rest-nodeauth";

const username = process.env["AZURE_USERNAME"];
const password = process.env["AZURE_PASSWORD"];

msRestNodeAuth.loginWithUsernamePasswordWithAuthResponse(username, password).then((authres) => {
  console.dir(authres, { depth: null })
}).catch((err) => {
  console.log(err);
});

service-principal/secret based login

import * as msRestNodeAuth from "@azure/ms-rest-nodeauth";

const clientId = process.env["CLIENT_ID"];
const secret = process.env["APPLICATION_SECRET"];
const tenantId = process.env["DOMAIN"];

msRestNodeAuth.loginWithServicePrincipalSecretWithAuthResponse(clientId, secret, tenantId).then((authres) => {
  console.dir(authres, { depth: null })
}).catch((err) => {
  console.log(err);
});

interactive/device-code flow login

import * as msRestNodeAuth from "@azure/ms-rest-nodeauth";

msRestNodeAuth.interactiveLoginWithAuthResponse().then((authres) => {
  console.dir(authres, { depth: null })
}).catch((err) => {
  console.log(err);
});

service-principal authentication from auth file on disk

import * as msRestNodeAuth from "../lib/msRestNodeAuth";

const options: msRestNodeAuth.LoginWithAuthFileOptions = {
  filePath: "<file path to auth file>",
}
msRestNodeAuth.loginWithAuthFileWithAuthResponse(options).then((authRes) => {
  console.log(authRes);
  console.log(process.env["AZURE_SUBSCRIPTION_ID"]);
}).catch((err) => {
  console.log(err);
});

MSI (Managed Service Identity) based login from a virtual machine created in Azure.

import * as msRestNodeAuth from "../lib/msRestNodeAuth";

const options: msRestNodeAuth.MSIVmOptions = {
  port: 50342;
}

msRestNodeAuth.loginWithVmMSI(options).then((msiTokenRes) => {
  console.log(msiTokenRes);
}).catch((err) => {
  console.log(err);
});

MSI (Managed Service Identity) based login from an AppService or Azure Function created in Azure.

import * as msRestNodeAuth from "../lib/msRestNodeAuth";

const options: msRestNodeAuth.MSIAppServiceOptions = {
  msiEndpoint: "http://127.0.0.1:41741/MSI/token/";
}

msRestNodeAuth.loginWithAppServiceMSI(options).then((msiTokenRes) => {
  console.log(msiTokenRes);
}).catch((err) => {
  console.log(err);
});

Contributing

This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.microsoft.com.

When you submit a pull request, a CLA-bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., label, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.