[jira] [Assigned] (ATLAS-5401) Add pluggable JWT support to the Atlas REST client so hook/bridge processes can obtain and refresh bearer tokens dynamically.

["Madhan Neethiraj (Jira)" <ji...@apache.org>]

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

Madhan Neethiraj reassigned ATLAS-5401:
---------------------------------------

    Assignee: Madhan Neethiraj

> Add pluggable JWT support to the Atlas REST client so hook/bridge processes can obtain and refresh bearer tokens dynamically.
> -----------------------------------------------------------------------------------------------------------------------------
>
>                 Key: ATLAS-5401
>                 URL: https://issues.apache.org/jira/browse/ATLAS-5401
>             Project: Atlas
>          Issue Type: Improvement
>            Reporter: Nixon Rodrigues
>            Assignee: Madhan Neethiraj
>            Priority: Major
>
> Introduce _atlas.rest.auth.token.supplier_="(FQCN of a Supplier<String>)" and load it via reflection in RestNotification. Add an AtlasClientV2 constructor that accepts a token supplier; on each request, handleJwt() calls supplier.get() and sets Authorization: Bearer <token>.
> Scope: Reuse the existing TokenRetriever / handleJwt() path (e.g. via a Supplier adapter), define auth precedence (Kerberos → JWT supplier → basic auth), and add unit tests for factory loading, client wiring, and header injection.
> Motivation: Current JWT support (atlas.jwt.source) only covers static env/file/cred sources; integrators need custom renewal (OAuth2, K8s, Vault, etc.).



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