[ 
https://issues.apache.org/jira/browse/KNOX-3100?focusedWorklogId=958974&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-958974
 ]

ASF GitHub Bot logged work on KNOX-3100:
----------------------------------------

                Author: ASF GitHub Bot
            Created on: 26/Feb/25 14:44
            Start Date: 26/Feb/25 14:44
    Worklog Time Spent: 10m 
      Work Description: lmccay opened a new pull request, #997:
URL: https://github.com/apache/knox/pull/997

   ## What changes were proposed in this pull request?
   
   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.
   
   ## How was this patch tested?
   
   Ran existing unit tests plus new tests for the new functionality.
   




Issue Time Tracking
-------------------

            Worklog Id:     (was: 958974)
    Remaining Estimate: 0h
            Time Spent: 10m

> 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.2.0
>
>          Time Spent: 10m
>  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)

Reply via email to