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

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

Commit d1204b9c835dffd3c24d7a38a9c5b5f4360eaf60 in knox's branch 
refs/heads/master from Sandor Molnar
[ https://gitbox.apache.org/repos/asf?p=knox.git;h=d1204b9c8 ]

KNOX-3460: audit all RFC 8693 token-exchange paths pre-mint and add a mint-time 
TOKEN_EXCHANGE audit emitting jti/expiry/issued_subject (#1409)

> Audit all token-exchange flows including minted token fields
> ------------------------------------------------------------
>
>                 Key: KNOX-3460
>                 URL: https://issues.apache.org/jira/browse/KNOX-3460
>             Project: Apache Knox
>          Issue Type: Sub-task
>          Components: Server
>    Affects Versions: 3.1.0
>            Reporter: Sandor Molnar
>            Assignee: Sandor Molnar
>            Priority: Major
>             Fix For: 3.1.0
>
>          Time Spent: 1h 10m
>  Remaining Estimate: 0h
>
> Only the delegation policy decision is audited today (TokenExchangeHandler 
> success/failure inside the delegation branch). The same-subject exchange path 
> emits no TOKEN_EXCHANGE audit record at all (only the generic AUTHENTICATION 
> audit from the shared {{{}continueWithEstablishedSecurityContext{}}}). 
> Minted-token fields — jti, expiry, issued_subject — are unauditable from the 
> filter because they only exist after TokenResource mints the token, and 
> TokenResource has no auditing whatsoever today.
> *Scope:*
>  # Audit all three exchange paths in the handler with the fields known 
> pre-mint (incl. same-subject).
>  # Add a TOKEN_EXCHANGE mint-time audit in TokenResource.getJWT() for 
> exchange-originated mints, emitting jti/expiry/issued_subject
> *Explicitly out of scope:* auditing ordinary (non-exchange) token issuance.



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

Reply via email to