[
https://issues.apache.org/jira/browse/SLING-11741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cioriia Cristian updated SLING-11741:
-------------------------------------
Description:
The Apache Sling Login Admin Whitelist has occurrences of "whitelist" and
"blacklist" e.g. "whitelist.bypass", "whitelist.bundles.regexp" which is
considered inequitable terminology and some customers are prevented to use
these terms by their git commit policies.
Therefore, some more acceptable equivalents should be provided for these terms.
The proposal is to provide the "allowedlist.bypass" and
"allowedlist.bundles.regexp" alternatives for them
was:
The Apache Sling Login Admin Whitelist has occurrences of "whitelist" and
"blacklist" e.g. "resource.resolver.vanitypath.blacklist",
"resource.resolver.vanitypath.whitelist" which is considered inequitable
terminology and some customers are prevented to use these terms by their git
commit policies.
Therefore, some more acceptable equivalents should be provided for these terms.
The proposal is to provide the "resource.resolver.vanitypath.blockedlist" and
"resource.resolver.vanitypath.allowedlist" alternatives for them
> Provide alternative terminology for inequitable terms
> -----------------------------------------------------
>
> Key: SLING-11741
> URL: https://issues.apache.org/jira/browse/SLING-11741
> Project: Sling
> Issue Type: Improvement
> Reporter: Cioriia Cristian
> Priority: Major
>
> The Apache Sling Login Admin Whitelist has occurrences of "whitelist" and
> "blacklist" e.g. "whitelist.bypass", "whitelist.bundles.regexp" which is
> considered inequitable terminology and some customers are prevented to use
> these terms by their git commit policies.
> Therefore, some more acceptable equivalents should be provided for these
> terms. The proposal is to provide the "allowedlist.bypass" and
> "allowedlist.bundles.regexp" alternatives for them
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
