infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Lambertus (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (INFRA-15691) evaluate asf-banned LDAP attribute
Date Thu, 04 Oct 2018 04:12:00 GMT

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

Chris Lambertus resolved INFRA-15691.
-------------------------------------
    Resolution: Fixed

Sebb outlined this neatly, and I've found no other places where this is used. No action is
needed. The presence of the attribute and its value are equivalent, which is not ideal (asf-banned
could be 'no' / 'false' ) but this is not a common condition or a situation worthy of deep
followup.


> evaluate asf-banned LDAP attribute
> ----------------------------------
>
>                 Key: INFRA-15691
>                 URL: https://issues.apache.org/jira/browse/INFRA-15691
>             Project: Infrastructure
>          Issue Type: Project
>          Components: Identity Management, LDAP
>            Reporter: Chris Lambertus
>            Assignee: Chris Lambertus
>            Priority: Minor
>
> Evaluate the use of 'asf-banned' to determine where/why it is used, and potentially replace
with a more useful/obvious 'disabled' attribute. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message