Skip to content

Commit c588396

Browse files
Merge pull request #273104 from shikhagarg1/main
unknown users details for OSDU groups
2 parents ccdb5d7 + 8dd5f75 commit c588396

File tree

3 files changed

+8
-2
lines changed

3 files changed

+8
-2
lines changed

articles/energy-data-services/concepts-entitlements.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -69,6 +69,9 @@ Now if you remove user_1 from ACL_1, user_1 remains to have access of the data_
6969

7070
And if ACL_1 and ACL_2 are removed from data_record_1, users.data.root continue to have owner access of the data. This preserves the data record from becoming orphan ever.
7171

72+
### Unknown OID
73+
You will see one unknown OID in all the OSDU groups added by default, this OID refers to an internal Azure Data Manager for Energy instance ID that is used for system to system communication. This OID gets created uniquely for each instance.
74+
7275
## Users
7376

7477
For each OSDU group, you can add a user as either an OWNER or a MEMBER:

articles/energy-data-services/how-to-deploy-osdu-admin-ui.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -88,7 +88,7 @@ The OSDU Admin UI enables platform administrators to manage the Azure Data Manag
8888
1. Enter the required environment variables on the terminal.
8989
```bash
9090
export ADMINUI_CLIENT_ID="" ## App Registration to be used by OSDU Admin UI, usually the client ID used to provision ADME
91-
export WEBSITE_NAME="" ## Unique name of the static web app or storage account that will be generated
91+
export WEBSITE_NAME="" ## Unique name of the static web app or storage account that will be generated. Storage account name must be between 3 and 24 characters in length and use numbers and lower-case letters only.
9292
export RESOURCE_GROUP="" ## Name of resource group
9393
export LOCATION="" ## Azure region to deploy to, i.e. "westeurope"
9494
```
@@ -129,7 +129,7 @@ The OSDU Admin UI enables platform administrators to manage the Azure Data Manag
129129
--public-access blob
130130
```
131131
132-
1. Add the redirect URI to the App Registration.
132+
1. Add the redirect URI to the App Registration.
133133
```azurecli
134134
export REDIRECT_URI=$(az storage account show --resource-group $RESOURCE_GROUP --name $WEBSITE_NAME --query "primaryEndpoints.web") && \
135135
echo "Redirect URL: $REDIRECT_URI" && \

articles/energy-data-services/how-to-generate-auth-token.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -96,6 +96,9 @@ You have two ways to get the list of data partitions in your Azure Data Manager
9696

9797
:::image type="content" source="media/how-to-generate-auth-token/data-partition-id-second-option-step-2.png" alt-text="Screenshot that shows finding the data-partition-id from the Azure Data Manager for Energy instance Overview page with the data partitions.":::
9898

99+
### Find domain
100+
By default, the `domain` is dataservices.energy for all the Azure Data Manager for Energy instances.
101+
99102
## Generate the client-id auth token
100103

101104
Run the following curl command in [Azure Cloud Bash](../cloud-shell/overview.md) after you replace the placeholder values with the corresponding values found earlier in the previous steps. The access token in the response is the `client-id` auth token.

0 commit comments

Comments
 (0)