From 6636b740b0516b42d8fc7783509f23569b2ce2c7 Mon Sep 17 00:00:00 2001 From: aguilard Date: Tue, 31 Aug 2021 10:17:11 +0200 Subject: [PATCH 1/2] Changes in Azure documentation Corrections to the client_id attribute and regular users. Change-Id: I0f98568389a2e53319b82c4bac2b38c732bc952e Signed-off-by: aguilard --- 04-vim-setup.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/04-vim-setup.md b/04-vim-setup.md index a61e83a..d8d9cd0 100644 --- a/04-vim-setup.md +++ b/04-vim-setup.md @@ -334,11 +334,11 @@ In order to use a VIM target based on Azure, the following information needs to - Azure `subscription Id`. - The `tenant Id`, to be created or obtained in the Microsoft portal. - Access credentials: - - `client_id`: In the case of a service principal (recommended for production deployments), this attribute corresponds to the Azure `application Id`. For regular users, this value is the `object Id` from user profile in portal (this approach can be more convenient for casual OSM testing). + - `client_id`: In the case of a service principal (recommended for production deployments), this attribute corresponds to the `application Id`. Azure regular users are currently not supported. - The `authentication Key`. - Resource Group: All Azure resources for a VIM target will be created into the same `resource_group`. Said resource group could exist before or, in case it did not exist, OSM would try to create it upon the creation of the VIM target (the latter would require that your user/service principal had sufficient privileges in the subscription - check with your administrator). -The above data can be accessed through the Azure portal, but can also be obtained through the CLI. For instance, once logged in, the commands `az ad signed-in-user show ` and `az account list` returns, among other information, `application Id`, `object Id`, `tenant Id` and `subscription Id`. +The above data can be accessed through the Azure portal, but can also be obtained through the CLI. For instance, once logged in, the command `az account list` returns, among other information, `application Id`, `tenant Id` and `subscription Id`. #### 2. Create Microsoft Azure Virtual Network @@ -363,8 +363,8 @@ osm vim-create --name azure --account_type azure --auth_url http://www.azure.com where: -- `client_id`: Corresponds to the `application id` (for service principals) or the `object Id` (for regular users). -- `client secret`: Authentication key (for a service principal) or `password` (for regular users). +- `client_id`: Corresponds to the service principal `application id`. +- `client secret`: Authentication key. - `subscription_id`: Azure `subscription Id` - `tenant`: Azure `tenant Id` -- GitLab From 40ed05b0f92b2f681bd07ef578de35bd7271a943 Mon Sep 17 00:00:00 2001 From: Francisco-Javier Ramon Salguero Date: Tue, 31 Aug 2021 08:32:42 +0000 Subject: [PATCH 2/2] Apply 3 suggestion(s) to 1 file(s) --- 04-vim-setup.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/04-vim-setup.md b/04-vim-setup.md index d8d9cd0..6b70d17 100644 --- a/04-vim-setup.md +++ b/04-vim-setup.md @@ -334,11 +334,11 @@ In order to use a VIM target based on Azure, the following information needs to - Azure `subscription Id`. - The `tenant Id`, to be created or obtained in the Microsoft portal. - Access credentials: - - `client_id`: In the case of a service principal (recommended for production deployments), this attribute corresponds to the `application Id`. Azure regular users are currently not supported. + - `client_id`: This attribute corresponds to the `application Id` of a service principal with the right permissions. Regular Azure users currently are not supported. - The `authentication Key`. - Resource Group: All Azure resources for a VIM target will be created into the same `resource_group`. Said resource group could exist before or, in case it did not exist, OSM would try to create it upon the creation of the VIM target (the latter would require that your user/service principal had sufficient privileges in the subscription - check with your administrator). -The above data can be accessed through the Azure portal, but can also be obtained through the CLI. For instance, once logged in, the command `az account list` returns, among other information, `application Id`, `tenant Id` and `subscription Id`. +The above data can be learned through the Azure portal or the Azure CLI. For instance, once logged in, the command `az account list` returns, among other information, the `application Id`, the `tenant Id`, and the `subscription Id`. #### 2. Create Microsoft Azure Virtual Network @@ -363,7 +363,7 @@ osm vim-create --name azure --account_type azure --auth_url http://www.azure.com where: -- `client_id`: Corresponds to the service principal `application id`. +- `client_id`: Corresponds to the service principal's `application id`. - `client secret`: Authentication key. - `subscription_id`: Azure `subscription Id` - `tenant`: Azure `tenant Id` -- GitLab