You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Abhishek Pal (Jira)" <ji...@apache.org> on 2026/07/13 16:46:00 UTC

[jira] [Updated] (HDDS-15845) Implement Protocol-Neutral Pluggable Authentication and Authorization Service

     [ https://issues.apache.org/jira/browse/HDDS-15845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Abhishek Pal updated HDDS-15845:
--------------------------------
    Description: 
This is to track the creation of a standalone process that becomes the single owner of client-facing authentication and authorization for all Ozone metadata operations.

It validates any supported credential type (Kerberos, S3 signatures, OAuth/OIDC, STS), evaluates authorization policy, and issues a short-lived cryptographically-signed token that OM verifies locally.

P.S: We are going to create subtasks for this EPIC once the design and goals reach consensus.

  was:
This is to track the creation of a standalone process that becomes the single owner of client-facing authentication and authorization for all Ozone metadata operations.

It validates any supported credential type (Kerberos, S3 signatures, OAuth/OIDC, STS), evaluates authorization policy, and issues a short-lived cryptographically-signed token that OM verifies locally.


> Implement Protocol-Neutral Pluggable Authentication and Authorization Service
> -----------------------------------------------------------------------------
>
>                 Key: HDDS-15845
>                 URL: https://issues.apache.org/jira/browse/HDDS-15845
>             Project: Apache Ozone
>          Issue Type: Epic
>          Components: Ozone Client, Ozone Manager
>            Reporter: Abhishek Pal
>            Assignee: Abhishek Pal
>            Priority: Major
>
> This is to track the creation of a standalone process that becomes the single owner of client-facing authentication and authorization for all Ozone metadata operations.
> It validates any supported credential type (Kerberos, S3 signatures, OAuth/OIDC, STS), evaluates authorization policy, and issues a short-lived cryptographically-signed token that OM verifies locally.
> P.S: We are going to create subtasks for this EPIC once the design and goals reach consensus.



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

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org