[
https://issues.apache.org/jira/browse/KNOX-3534?focusedWorklogId=1051120&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-1051120
]
ASF GitHub Bot logged work on KNOX-3534:
----------------------------------------
Author: ASF GitHub Bot
Created on: 29/Oct/26 06:50
Start Date: 29/Oct/26 06:50
Worklog Time Spent: 10m
Work Description: github-actions[bot] commented on PR #1476:
URL: https://github.com/apache/knox/pull/1476#issuecomment-6490010872
## Test Results
4 files 4 suites 1m 20s ⏱️
149 tests 149 ✅ 0 💤 0 ❌
173 runs 173 ✅ 0 💤 0 ❌
Results for commit b2b41dc9.
[test-results]:data:application/gzip;base64,H4sIAKns4moC/12MQQ7CIBQFr9KwdkHhg9TLNB8oCbEthsKq8e5iUxFdzry82Ynz87SRWweXjmzZpwo2R0w+rAUVLVyW9N56GD40btmYf3X3j6LqY3To5x8xxRjiaWJej+aVn1CTjfkWD26CB7c9E5bFpwJEMw29NYNwwKwUUlAcGGoGRiKg05wrShUCeb4A0C1oKAQBAAA=
Issue Time Tracking
-------------------
Worklog Id: (was: 1051120)
Time Spent: 20m (was: 10m)
> Add k8s request audience validator bypass for JWTs from an ingress
> ------------------------------------------------------------------
>
> Key: KNOX-3534
> URL: https://issues.apache.org/jira/browse/KNOX-3534
> Project: Apache Knox
> Issue Type: Sub-task
> Components: JWT
> Reporter: Harrison Sheinblatt
> Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> The existing K8sDestinationAudienceValidator feature focus on service to
> service audience validation. Enable using the validator for the use case
> where a single topology is to validate all jwts, both service to service and
> ingress traffic JWTs.
> Add flags to enable a feature to match JWTs coming from an ingress gateway
> and treat them differently: either validate the audience against the same
> static whitelist used for the rest of the traffic, or skip audience
> validation. This path would be split and evaluated first. Delegation tokens
> are not allowed on that path, so even if they come from an ingress, still
> treat them as they are now.
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
