@azure/arm-authorization-profile-2019-03-01-hybrid
Advanced tools
AuthorizationManagementClient Library with typescript type definitions for node.js and browser.
This package contains an isomorphic SDK (runs both in Node.js and in browsers) for AuthorizationManagementClient.
Please note, this package is deprecated and not functional as it uses an older version of the Javascript SDK generator. As of April 2022, you can instead use @azure/arm-authorization-profile-2020-09-01-hybrid.
You must have an Azure subscription.
To use this SDK in your project, you will need to install two packages.
@azure/arm-authorization-profile-2019-03-01-hybrid that contains the client.@azure/identity that provides different mechanisms for the client to authenticate your requests using Azure Active Directory.Install both packages using the below command:
npm install --save @azure/arm-authorization-profile-2019-03-01-hybrid @azure/identity
Note: You may have used either
@azure/ms-rest-nodeauthor@azure/ms-rest-browserauthin the past. These packages are in maintenance mode receiving critical bug fixes, but no new features. If you are on a Node.js that has LTS status, or are writing a client side browser application, we strongly encourage you to upgrade to@azure/identitywhich uses the latest versions of Azure Active Directory and MSAL APIs and provides more authentication options.
@azure/identity based on the authentication method of your choiceDefaultAzureCredential in the Node.js sample below.In the below samples, we pass the credential and the Azure subscription id to instantiate the client. Once the client is created, explore the operations on it either in your favorite editor or in our API reference documentation to get started.
const { DefaultAzureCredential } = require("@azure/identity");
const { AuthorizationManagementClient } = require("@azure/arm-authorization-profile-2019-03-01-hybrid");
const subscriptionId = process.env["AZURE_SUBSCRIPTION_ID"];
// Use `DefaultAzureCredential` or any other credential of your choice based on https://aka.ms/azsdk/js/identity/examples
// Please note that you can also use credentials from the `@azure/ms-rest-nodeauth` package instead.
const creds = new DefaultAzureCredential();
const client = new AuthorizationManagementClient(creds, subscriptionId);
const resourceGroupName = "testresourceGroupName";
client.permissions.listForResourceGroup(resourceGroupName).then((result) => {
console.log("The result is:");
console.log(result);
}).catch((err) => {
console.log("An error occurred:");
console.error(err);
});
In browser applications, we recommend using the InteractiveBrowserCredential that interactively authenticates using the default system browser.
<!DOCTYPE html>
<html lang="en">
<head>
<title>@azure/arm-authorization-profile-2019-03-01-hybrid sample</title>
<script src="node_modules/@azure/ms-rest-azure-js/dist/msRestAzure.js"></script>
<script src="node_modules/@azure/identity/dist/index.js"></script>
<script src="node_modules/@azure/arm-authorization-profile-2019-03-01-hybrid/dist/arm-authorization-profile-2019-03-01-hybrid.js"></script>
<script type="text/javascript">
const subscriptionId = "<Subscription_Id>";
// Create credentials using the `@azure/identity` package.
// Please note that you can also use credentials from the `@azure/ms-rest-browserauth` package instead.
const credential = new InteractiveBrowserCredential(
{
clientId: "<client id for your Azure AD app>",
tenantId: "<optional tenant for your organization>"
});
const client = new Azure.ArmAuthorizationProfile20190301Hybrid.AuthorizationManagementClient(creds, subscriptionId);
const resourceGroupName = "testresourceGroupName";
client.permissions.listForResourceGroup(resourceGroupName).then((result) => {
console.log("The result is:");
console.log(result);
}).catch((err) => {
console.log("An error occurred:");
console.error(err);
});
</script>
</head>
<body></body>
</html>
FAQs
AuthorizationManagementClient Library with typescript type definitions for node.js and browser.
We found that @azure/arm-authorization-profile-2019-03-01-hybrid demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Research
An advanced npm supply chain attack is leveraging Ethereum smart contracts for decentralized, persistent malware control, evading traditional defenses.
Security News
Research
Attackers are impersonating Sindre Sorhus on npm with a fake 'chalk-node' package containing a malicious backdoor to compromise developers' projects.
Security News
The npm package for the LottieFiles Player web component was hit with a supply chain attack after a software engineer's npmjs credentials were compromised.