You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@knox.apache.org by "Sandeep More (Jira)" <ji...@apache.org> on 2025/05/19 13:33:00 UTC
[jira] [Updated] (KNOX-3100) Extend Group Header Support in RemoteAuthProvider to handle Multiple Headers
[ https://issues.apache.org/jira/browse/KNOX-3100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sandeep More updated KNOX-3100:
-------------------------------
Fix Version/s: 2.1.0
(was: 2.2.0)
> Extend Group Header Support in RemoteAuthProvider to handle Multiple Headers
> ----------------------------------------------------------------------------
>
> Key: KNOX-3100
> URL: https://issues.apache.org/jira/browse/KNOX-3100
> Project: Apache Knox
> Issue Type: Improvement
> Components: Server
> Reporter: Larry McCay
> Assignee: Larry McCay
> Priority: Major
> Fix For: 2.1.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Initial iteration of the RemoteAuthProvider has support for a single HTTP Header containing the group memberships. The Pre API in the Knox Auth Service breaks memberships up across multiple headers to manage the size.
> We need to determine a syntax as an explicit list or a range with some builtin syntax of a numeric suffix. Otherwise, it will need a list of possible header names with it accommodating the largest set which seems odd.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)