[
https://issues.apache.org/jira/browse/ATLAS-5401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18114085#comment-18114085
]
ASF subversion and git services commented on ATLAS-5401:
--------------------------------------------------------
Commit fb78b7dc41bc74e20ee6b477df39b8bafeb84ffb in atlas's branch
refs/heads/ATLAS-4796_u from Madhan Neethiraj
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=fb78b7dc4 ]
ATLAS-5401: Atlas client configuration to support custom token supplier (#752)
* ATLAS-5401: Atlas client configuration to support custom token supplier
> 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
> Fix For: 3.0.0, 2.6.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> 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)
