You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
CodeGen from PR 15016 in Azure/azure-rest-api-specs
Changes to fix the Resource Provider name casing issue for Azure Postgres, MySQL and MariaDB (Azure#15016)
* Changes to fix the Resource provided name casing issue for Azure Postgres, MySQL and MariaDB services
* Changes to fix the Resource provided name casing issue for Azure Postgres, MySQL and MariaDB services
* Revert "Changes to fix the Resource provided name casing issue for Azure Postgres, MySQL and MariaDB services"
This reverts commit ecc38dc560b77de750350143fd80bdd6e3823882.
> **Note**: You may have used either `@azure/ms-rest-nodeauth` or `@azure/ms-rest-browserauth` in the past. These packages are in maintenance mode receiving critical bug fixes, but no new features.
25
+
If you are on a [Node.js that has LTS status](https://nodejs.org/about/releases/), or are writing a client side browser application, we strongly encourage you to upgrade to `@azure/identity` which uses the latest versions of Azure Active Directory and MSAL APIs and provides more authentication options.
15
26
16
27
### How to use
17
28
18
-
#### nodejs - Authentication, client creation and get servers as an example written in TypeScript.
29
+
- If you are writing a client side browser application,
30
+
- Follow the instructions in the section on Authenticating client side browser applications in [Azure Identity examples](https://aka.ms/azsdk/js/identity/examples) to register your application in the Microsoft identity platform and set the right permissions.
31
+
- Copy the client ID and tenant ID from the Overview section of your app registration in Azure portal and use it in the browser sample below.
32
+
- If you are writing a server side application,
33
+
-[Select a credential from `@azure/identity` based on the authentication method of your choice](https://aka.ms/azsdk/js/identity/examples)
34
+
- Complete the set up steps required by the credential if any.
35
+
- Use the credential you picked in the place of `DefaultAzureCredential` in the Node.js sample below.
19
36
20
-
##### Install @azure/ms-rest-nodeauth
21
-
22
-
```bash
23
-
npm install @azure/ms-rest-nodeauth
24
-
```
37
+
In the below samples, we pass the credential and the Azure subscription id to instantiate the client.
38
+
Once the client is created, explore the operations on it either in your favorite editor or in our [API reference documentation](https://docs.microsoft.com/javascript/api) to get started.
39
+
#### nodejs - Authentication, client creation, and get servers as an example written in JavaScript.
#### browser - Authentication, client creation and get servers as an example written in JavaScript.
63
+
#### browser - Authentication, client creation, and get servers as an example written in JavaScript.
49
64
50
-
##### Install @azure/ms-rest-browserauth
51
-
52
-
```bash
53
-
npm install @azure/ms-rest-browserauth
54
-
```
65
+
In browser applications, we recommend using the `InteractiveBrowserCredential` that interactively authenticates using the default system browser.
66
+
- See [Single-page application: App registration guide](https://docs.microsoft.com/azure/active-directory/develop/scenario-spa-app-registration) to configure your app registration for the browser.
67
+
- Note down the client Id from the previous step and use it in the browser sample below.
55
68
56
69
##### Sample code
57
70
58
-
See https://github.com/Azure/ms-rest-browserauth to learn how to authenticate to Azure in the browser.
0 commit comments