infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sebb (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (INFRA-17782) Create cn=concom,ou=project
Date Wed, 30 Jan 2019 14:57:00 GMT

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

Sebb commented on INFRA-17782:
------------------------------

I see. I thought concom was the LDAP name for conferences.

Note that the concom LDAP group is used to control access to various directories.
Most are also writeable by the apachecon group or members
However the following is only writeable by concom (and infra):

/websites/production/events

If there is still a need for that karma, then the LDAP group should probably be changed to
an Auth group similarly to apachecon.

> Create cn=concom,ou=project
> ---------------------------
>
>                 Key: INFRA-17782
>                 URL: https://issues.apache.org/jira/browse/INFRA-17782
>             Project: Infrastructure
>          Issue Type: Task
>          Components: LDAP
>            Reporter: Sebb
>            Priority: Major
>
> concom currently only exists as an LDAP unix group.
> For consistency with tac and security etc. there should be a project group.
> This should probably start with owner=current chair, and members=current unix group



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

Mime
View raw message