Menu
Set up authentication for the ADME OSDU connector — get an Azure bearer token and write dev_config.json for live testing.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Mechanical audit of the ADME OSDU connector — implementation correctness, test coverage, artifacts completeness, and security. Produces a scored report.
Run the AdmeOsduLakeflowConnect pytest suite, diagnose failures, and fix the connector or simulator until everything passes. Branches on mode={simulate|live}.
Validate that credentials for the ADME OSDU connector authenticate successfully against the real ADME API.
Validate that ADME domain tables (wellbore, reservoir, rock_and_fluid) correctly implement CDC incremental sync — offset tracking, watermark filtering, and pagination termination.
Baseado na classificação ocupacional SOC
| name | authenticate-source |
| description | Set up authentication for the ADME OSDU connector — get an Azure bearer token and write dev_config.json for live testing. |
Produce a valid tests/unit/adme_osdu/dev_config.json that the live-mode tests can use.
| Field | Value |
|---|---|
| Tenant ID | 72f988bf-86f1-41af-91ab-2d7cd011db47 |
| ADME API Client ID (resource) | e37a6c70-7cbc-4593-80fc-01c1f20203f7 |
| Token scope | api://e37a6c70-7cbc-4593-80fc-01c1f20203f7/.default |
| Sandbox base URL | https://admesbxscusins1.energy.azure.com |
| Data partition | opendes |
cat tests/unit/adme_osdu/dev_config.json 2>/dev/null && echo "config exists"
If present and token not expired, skip to Step 3.
Option A: az CLI (interactive, may need browser)
# Login to ADME tenant if not already
az login --tenant 72f988bf-86f1-41af-91ab-2d7cd011db47
# Get token
TOKEN=$(az account get-access-token \
--resource "api://e37a6c70-7cbc-4593-80fc-01c1f20203f7" \
--tenant "72f988bf-86f1-41af-91ab-2d7cd011db47" \
--query accessToken -o tsv)
echo "Token length: ${#TOKEN}"
Option B: From Databricks workspace (Managed Identity on cluster)
If running on the Databricks cluster that has adme-adb-sbx-scus-mi attached:
from azure.identity import ManagedIdentityCredential
cred = ManagedIdentityCredential(client_id="4841d326-e982-4898-813f-cb34f960ca1a")
token = cred.get_token("api://e37a6c70-7cbc-4593-80fc-01c1f20203f7/.default").token
cat > tests/unit/adme_osdu/dev_config.json << EOF
{
"base_url": "https://admesbxscusins1.energy.azure.com",
"data_partition_id": "opendes",
"tenant_id": "72f988bf-86f1-41af-91ab-2d7cd011db47",
"adme_api_client_id": "e37a6c70-7cbc-4593-80fc-01c1f20203f7",
"access_token": "$TOKEN"
}
EOF
dev_config.jsonis gitignored — never commit tokens.
Run the validate-connector-auth skill or quick smoke check:
curl -s -o /dev/null -w "%{http_code}" \
-H "Authorization: Bearer $TOKEN" \
-H "data-partition-id: opendes" \
"https://admesbxscusins1.energy.azure.com/api/entitlements/v2/groups"
Expected: 200. Then run /validate-connector-auth for full connector-level check.
| Error | Cause | Fix |
|---|---|---|
AADSTS53003 Conditional Access | Local machine not compliant | az login --tenant 72f988bf... via browser |
AADSTS700016 App not found | Wrong tenant | Confirm --tenant 72f988bf-86f1-41af-91ab-2d7cd011db47 |
401 from ADME | Token for wrong resource | Use api://e37a6c70-7cbc-4593-80fc-01c1f20203f7 as resource |
| Token expires in < 5 min | CLI cached expired token | az account get-access-token --resource ... --tenant ... re-authenticates |