Skip to content

Domain-scoped "Domain Only Access Role" blocks glossary term page access despite assets appearing correctly in RBAC-enabled search #33356

Closed

Description

@jnrimjhim

Affected module

Governance (Glossary / Classification / Domains)

Describe the bug

A user with a Domain Only Access Role assigned is unable to view a glossary term page when that term's domain matches the user's assigned domain, and receives a permissions error. Notably, the same domain-scoped asset does appear correctly when the user performs a search with RBAC enabled — indicating the search-layer permission evaluation and the glossary term detail-page permission evaluation are inconsistent.

To Reproduce

  1. Assign a domain to a Glossary Term.
  2. Create/assign a user the Domain Only Access Role, scoped to that same domain.
  3. As that user, perform a search — confirm the domain-scoped glossary term/asset appears correctly in RBAC-enabled search results.
  4. As that user, navigate directly to the Glossary Term page for that same term.
  5. Observe a permissions error is shown, despite the user having domain access to that term.

Expected behavior

A user with Domain Only Access Role scoped to a domain should be able to view glossary term pages for terms within that domain — consistent with what they can already see via RBAC-enabled search.

OS

No response

Python version

No response

OpenMetadata version

2.0.1

OpenMetadata Ingestion package version

No response

Additional context

No response

Pre-submission checklist

  • I searched for duplicate issues.
  • I removed credentials, hostnames, emails, and other sensitive data from logs and config.

Activity

  1. Prakhar-Mishra1107 commented on Sep 15, 2026

    @Prakhar-Mishra1107

    Hi Team, I have faced similar issue, instead of domain level access, I was trying to with owner/team level access but was getting permissions error.

  2. moved this to Release Backlog 🚧 in Shippingon Sep 16, 2026
  3. self-assigned this
    on Sep 16, 2026
  4. moved this from Release Backlog 🚧 to In Progress 🏗️ in Shippingon Sep 16, 2026
  5. moved this from In Progress 🏗️ to Validation in Shippingon Sep 16, 2026
  6. moved this from Validation to Release Backlog 🚧 in Shippingon Sep 16, 2026
  7. anuj-kumary commented on Oct 1, 2026

    @anuj-kumary
    Member

    Closing this issue as it is not reproducible. It seems to have been fixed in the latest release, 2.0.3.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

bugSomething isn't working

Type

No type

Projects

  • Status
    Done ✅

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions