[PR] Bump ejs from 3.1.8 to 3.1.10 in /knox-webshell-ui [knox]

2024-05-01 Thread via GitHub


dependabot[bot] opened a new pull request, #904:
URL: https://github.com/apache/knox/pull/904

   Bumps [ejs](https://github.com/mde/ejs) from 3.1.8 to 3.1.10.
   
   Release notes
   Sourced from https://github.com/mde/ejs/releases;>ejs's 
releases.
   
   v3.1.10
   Version 3.1.10
   v3.1.9
   Version 3.1.9
   
   
   
   Commits
   
   https://github.com/mde/ejs/commit/d3f807dea9ce904e20a47a661f2310ce9134dc2a;>d3f807d
 Version 3.1.10
   https://github.com/mde/ejs/commit/9ee26dde5d7015d9c0e2ff87314cabeac5247c02;>9ee26dd
 Mocha TDD
   https://github.com/mde/ejs/commit/e469741dca7df2eb400199e1cdb74621e3f89aa5;>e469741
 Basic pollution protection
   https://github.com/mde/ejs/commit/715e9507fa3e6122dc6430fe0f25a6e6ded300c1;>715e950
 Merge pull request https://redirect.github.com/mde/ejs/issues/756;>#756 from 
Jeffrey-mu/main
   https://github.com/mde/ejs/commit/cabe3146ad964a1e98db7742abf435906ca79406;>cabe314
 Include advanced usage examples
   https://github.com/mde/ejs/commit/29b076cdbbf3eb1b4323b33299ab6d79391b2c33;>29b076c
 Added header
   https://github.com/mde/ejs/commit/11503c79af882e3635b513d57c7f1813792eb127;>11503c7
 Merge branch 'main' of github.com:mde/ejs into main
   https://github.com/mde/ejs/commit/7690404e2fc1688756938e4d2fc19e0fac77d736;>7690404
 Added security banner to README
   https://github.com/mde/ejs/commit/f47d7aedd51a983e4f73045f962b1209096b5800;>f47d7ae
 Update SECURITY.md
   https://github.com/mde/ejs/commit/828cea1687e3db459ab09d2f405d2444c7580b90;>828cea1
 Update SECURITY.md
   Additional commits viewable in https://github.com/mde/ejs/compare/v3.1.8...v3.1.10;>compare view
   
   
   
   
   
   [![Dependabot compatibility 
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=ejs=npm_and_yarn=3.1.8=3.1.10)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)
   
   Dependabot will resolve any conflicts with this PR as long as you don't 
alter it yourself. You can also trigger a rebase manually by commenting 
`@dependabot rebase`.
   
   [//]: # (dependabot-automerge-start)
   [//]: # (dependabot-automerge-end)
   
   ---
   
   
   Dependabot commands and options
   
   
   You can trigger Dependabot actions by commenting on this PR:
   - `@dependabot rebase` will rebase this PR
   - `@dependabot recreate` will recreate this PR, overwriting any edits that 
have been made to it
   - `@dependabot merge` will merge this PR after your CI passes on it
   - `@dependabot squash and merge` will squash and merge this PR after your CI 
passes on it
   - `@dependabot cancel merge` will cancel a previously requested merge and 
block automerging
   - `@dependabot reopen` will reopen this PR if it is closed
   - `@dependabot close` will close this PR and stop Dependabot recreating it. 
You can achieve the same result by closing it manually
   - `@dependabot show  ignore conditions` will show all of 
the ignore conditions of the specified dependency
   - `@dependabot ignore this major version` will close this PR and stop 
Dependabot creating any more for this major version (unless you reopen the PR 
or upgrade to it yourself)
   - `@dependabot ignore this minor version` will close this PR and stop 
Dependabot creating any more for this minor version (unless you reopen the PR 
or upgrade to it yourself)
   - `@dependabot ignore this dependency` will close this PR and stop 
Dependabot creating any more for this dependency (unless you reopen the PR or 
upgrade to it yourself)
   You can disable automated security fix PRs for this repo from the [Security 
Alerts page](https://github.com/apache/knox/network/alerts).
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@knox.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



[jira] [Created] (KNOX-3035) Group header value should be based on data size and not number

2024-05-01 Thread Sandeep More (Jira)
Sandeep More created KNOX-3035:
--

 Summary: Group header value should be based on data size and not 
number
 Key: KNOX-3035
 URL: https://issues.apache.org/jira/browse/KNOX-3035
 Project: Apache Knox
  Issue Type: Bug
  Components: Server
Reporter: Sandeep More
Assignee: Sandeep More


KNOX-2974 and KNOX-3023 support adding group headers to requests flowing to 
downstream endpoints. Currently the groups headers is based on number of groups 
(1000 default). A lot of webservers and loadbalancers support header sizes 
between 4KB - 8KB which be an issue when header sizes are large. 

This JIRA is to update this logic to limit groups in one header to configured 
size in KBs.



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


[jira] [Created] (KNOX-3034) Document KNOX-3023 - Support for groups and principal in downstream dispatch request

2024-05-01 Thread Sandeep More (Jira)
Sandeep More created KNOX-3034:
--

 Summary: Document KNOX-3023 - Support for groups and principal in 
downstream dispatch request
 Key: KNOX-3034
 URL: https://issues.apache.org/jira/browse/KNOX-3034
 Project: Apache Knox
  Issue Type: Bug
  Components: Document
Reporter: Sandeep More
Assignee: Sandeep More






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


[jira] [Resolved] (KNOX-3023) Extend the Hadoop proxyuser dispatch to optionally include groups in a header in addition to doAs

2024-05-01 Thread Sandeep More (Jira)


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

Sandeep More resolved KNOX-3023.

Resolution: Fixed

> Extend the Hadoop proxyuser dispatch to optionally include groups in a header 
> in addition to doAs
> -
>
> Key: KNOX-3023
> URL: https://issues.apache.org/jira/browse/KNOX-3023
> Project: Apache Knox
>  Issue Type: Bug
>  Components: Server
>Reporter: Sandeep More
>Assignee: Sandeep More
>Priority: Major
> Fix For: 2.0.0
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> Currently Hadoop proxyuser dispatch does not have a mechanism to relay user 
> groups. This JIRA tried to address this problem. This can be done similar to 
> what we have done in [Knox Auth 
> Service|https://knox.apache.org/books/knox-2-0-0/user-guide.html#Knox+Auth+Service]
>  `auth/api/v1/pre`  endpoint where a header is added to the response (by 
> default X-Knox-Actor-ID) with the principal name to the response. In this 
> case these headers will be added to outgoing requests.



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


[jira] [Commented] (KNOX-3023) Extend the Hadoop proxyuser dispatch to optionally include groups in a header in addition to doAs

2024-05-01 Thread ASF subversion and git services (Jira)


[ 
https://issues.apache.org/jira/browse/KNOX-3023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17842655#comment-17842655
 ] 

ASF subversion and git services commented on KNOX-3023:
---

Commit b6ff0acdc326e54fd061b4b2f4e172cef24f5a5f in knox's branch 
refs/heads/master from Sandeep Moré
[ https://gitbox.apache.org/repos/asf?p=knox.git;h=b6ff0acdc ]

KNOX-3023 - Include groups in a header in ConfigurableDispatch (#903)



> Extend the Hadoop proxyuser dispatch to optionally include groups in a header 
> in addition to doAs
> -
>
> Key: KNOX-3023
> URL: https://issues.apache.org/jira/browse/KNOX-3023
> Project: Apache Knox
>  Issue Type: Bug
>  Components: Server
>Reporter: Sandeep More
>Assignee: Sandeep More
>Priority: Major
> Fix For: 2.0.0
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> Currently Hadoop proxyuser dispatch does not have a mechanism to relay user 
> groups. This JIRA tried to address this problem. This can be done similar to 
> what we have done in [Knox Auth 
> Service|https://knox.apache.org/books/knox-2-0-0/user-guide.html#Knox+Auth+Service]
>  `auth/api/v1/pre`  endpoint where a header is added to the response (by 
> default X-Knox-Actor-ID) with the principal name to the response. In this 
> case these headers will be added to outgoing requests.



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


[jira] [Work logged] (KNOX-3023) Extend the Hadoop proxyuser dispatch to optionally include groups in a header in addition to doAs

2024-05-01 Thread ASF GitHub Bot (Jira)


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

ASF GitHub Bot logged work on KNOX-3023:


Author: ASF GitHub Bot
Created on: 01/May/24 13:57
Start Date: 01/May/24 13:57
Worklog Time Spent: 10m 
  Work Description: moresandeep merged PR #903:
URL: https://github.com/apache/knox/pull/903




Issue Time Tracking
---

Worklog Id: (was: 917120)
Time Spent: 20m  (was: 10m)

> Extend the Hadoop proxyuser dispatch to optionally include groups in a header 
> in addition to doAs
> -
>
> Key: KNOX-3023
> URL: https://issues.apache.org/jira/browse/KNOX-3023
> Project: Apache Knox
>  Issue Type: Bug
>  Components: Server
>Reporter: Sandeep More
>Assignee: Sandeep More
>Priority: Major
> Fix For: 2.0.0
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> Currently Hadoop proxyuser dispatch does not have a mechanism to relay user 
> groups. This JIRA tried to address this problem. This can be done similar to 
> what we have done in [Knox Auth 
> Service|https://knox.apache.org/books/knox-2-0-0/user-guide.html#Knox+Auth+Service]
>  `auth/api/v1/pre`  endpoint where a header is added to the response (by 
> default X-Knox-Actor-ID) with the principal name to the response. In this 
> case these headers will be added to outgoing requests.



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


Re: [PR] KNOX-3023 - Include groups in a header in ConfigurableDispatch [knox]

2024-05-01 Thread via GitHub


moresandeep merged PR #903:
URL: https://github.com/apache/knox/pull/903


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@knox.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org