You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@knox.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2026/09/16 07:08:00 UTC

[jira] [Commented] (KNOX-3456) Enforce canActFor.groups in delegation policy via Knox LDAP group lookup

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

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

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

KNOX-3456: resolve canActFor.groups via KnoxLDAPService group lookup, failing with server_error when LDAP is unavailable (#1402)

>  Enforce canActFor.groups in delegation policy via Knox LDAP group lookup
> -------------------------------------------------------------------------
>
>                 Key: KNOX-3456
>                 URL: https://issues.apache.org/jira/browse/KNOX-3456
>             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
>  Remaining Estimate: 0h
>
> As a platform operator, I want to define delegation policies that grant exchange rights to LDAP groups rather than individual user lists, so that access follows group membership without requiring Knox policy updates for each user change.
> ACCEPTANCE CRITERIA:
> - When a policy has a non-empty groups list for who the actor can act for, Knox checks whether the subject user is a member of any listed group using the Knox LDAP service group lookup.
> - With the LDAP roles-lookup interceptor configured, the group names returned by the LDAP service match the AWC role names stored in the policy. No additional mapping step is required.
> - If LDAP is disabled and a policy has a non-empty groups list, the token exchange returns server_error with a description directing the operator to enable LDAP. The exchange does not silently deny with subject_not_allowed.
> - If the LDAP group lookup call throws an exception, the exchange returns server_error with a description, and the exception and stack trace are logged.
> Integration test: a user who is a member of a policy group is authorized. A user who is not a member is denied with access_denied.



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