[
https://issues.apache.org/jira/browse/RANGER-5496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Abhishek Kumar resolved RANGER-5496.
------------------------------------
Fix Version/s: 3.0.0
Resolution: Fixed
Merged in master:
https://github.com/apache/ranger/commit/0ea5ec5e80f609b0645bf2d9b5de5b8370382a8f
> Decouple JWT lifecycle from Ranger plugin via pluggable JWT provider
> --------------------------------------------------------------------
>
> Key: RANGER-5496
> URL: https://issues.apache.org/jira/browse/RANGER-5496
> Project: Ranger
> Issue Type: Improvement
> Components: Ranger
> Reporter: Abhishek Kumar
> Assignee: Abhishek Kumar
> Priority: Major
> Fix For: 3.0.0
>
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> Currently JWT is fetched during plugin initialization (via 3 different ways:
> env, file, cred file) and captured statically in the REST client filter. This
> enhancement introduces a pluggable JWT provider interface allowing services
> to manage JWT lifecycle independently while enabling Ranger plugins to fetch
> the latest JWT dynamically for each outbound REST call to Ranger Admin.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
