You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ranger.apache.org by "Paresh Devalia (Jira)" <ji...@apache.org> on 2026/08/24 11:51:00 UTC

[jira] [Created] (RANGER-5759) Add notification-topic resource and post-notification privilege to Atlas service-def in Ranger

Paresh Devalia created RANGER-5759:
--------------------------------------

             Summary: Add notification-topic resource and post-notification privilege to Atlas service-def in Ranger
                 Key: RANGER-5759
                 URL: https://issues.apache.org/jira/browse/RANGER-5759
             Project: Ranger
          Issue Type: Improvement
          Components: Ranger
            Reporter: Paresh Devalia


Atlas REST notification API accepts hook messages via:
POST /api/atlas/v2/notification/topic/\{topicName}

These messages can create/update/delete Atlas entities. This endpoint must be authorized through Ranger.

*Introduce topic-scoped authorization in Atlas + Ranger:*
 * New Atlas resource-type: notification-topic
 * New privilege(access): post-notification

*Ranger changes*
 * Update ranger-servicedef-atlas.json:
 * Add resource: notification-topic
 * Add access type: post-notification



*Acceptance criteria*
 # Ranger admin can create policy on notification-topic (e.g. ATLAS_HOOK) with post-notification access
 # Authorized user can POST to allowed topic
 # Unauthorized user gets 403
 # Existing deployments upgraded via patch

 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)