You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Carsten Ziegeler (Jira)" <ji...@apache.org> on 2025/03/11 06:56:00 UTC

[jira] [Updated] (SLING-12324) Referrer Filter Reference Policy Should be Dynamic

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

Carsten Ziegeler updated SLING-12324:
-------------------------------------
    Fix Version/s:     (was: Security 1.2.2)

> Referrer Filter Reference Policy Should be Dynamic
> --------------------------------------------------
>
>                 Key: SLING-12324
>                 URL: https://issues.apache.org/jira/browse/SLING-12324
>             Project: Sling
>          Issue Type: Improvement
>          Components: Sling Security
>    Affects Versions: Security 1.2.0
>            Reporter: Dan Klco
>            Priority: Major
>
> The Reference Policy for amendments to the ReferrerFilter: [https://github.com/apache/sling-org-apache-sling-security/blob/master/src/main/java/org/apache/sling/security/impl/ReferrerFilter.java#L283C39-L283C60]
> are set to 
> {{policyOption = ReferencePolicyOption.GREEDY, cardinality = ReferenceCardinality.MULTIPLE}} so they will pick up multiple amendments if available at initialization, however because the ReferencePolicy is still static, new amendments available after the component initializes will not be detected.
>  
> To support this, the ReferencePolicy should be set to Dynamic. This will also require changing from constructor based parameters to bind parameters.



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