DataHub / OpenMetadata / Atlan
Modern data catalog platforms (open-source and commercial)
Access mode: Read-only
Required information
| Field | Details |
|---|---|
| Instance URL | DataHub GMS endpoint, OpenMetadata server URL, or Atlan tenant URL. |
| Authentication | DataHub: PAT. OpenMetadata: JWT or basic auth. Atlan: API token. |
| Scope | Specific data sources, glossaries, or all catalog content. |
Network considerations
DataHub: Self-hosted (VPN/direct access to GMS on port 8080) or Acryl Cloud (HTTPS).
OpenMetadata: Self-hosted (port 8585) or SaaS.
Atlan: SaaS over HTTPS. No VPN needed.
Credential and auth management
DataHub: PAT generated in UI. Scoped to user’s policies.
OpenMetadata: JWT token (bot account) or basic auth. Bot accounts preferred for integrations.
Atlan: API token from admin settings. Scoped by Atlan RBAC policies.
All three support programmatic access: Create a dedicated service/bot account in each.
Validation checks
| Check | Method | Expected result |
|---|---|---|
| DataHub auth | GET /entities/v1?aspects=datasetKey&count=1 (GMS) | Returns a dataset entity |
| OpenMetadata auth | GET /api/v1/tables?limit=1 | Returns a table |
| Atlan auth | GET /api/meta/search/indexsearch with test query | Returns catalog results |
| Lineage access | Query lineage endpoint for a known entity | Returns upstream/downstream lineage |
Every connection starts from the pre-engagement checklist and goes through the universal validation protocol before production sign-off.