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-18474) JIRA, Confluence and LDAP namespaces
Date Tue, 11 Jun 2019 05:00:05 GMT

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

Chris Lambertus resolved INFRA-18474.
-------------------------------------
    Resolution: Won't Fix

It is technically possible, but it is not worth the effort. as it needs to be re-tested and
deployed every time confluence is updated, and would have extremely limited utility. Unfortunately,
there are no great solutions to this particular problem, and some guest accounts are going
to get bumped in favor of committer accounts. Infra deems this acceptable for the time being.
We may evaluate a different crowd-based guest access process in the future if the current
situation becomes problematic.


> JIRA, Confluence and LDAP namespaces
> ------------------------------------
>
>                 Key: INFRA-18474
>                 URL: https://issues.apache.org/jira/browse/INFRA-18474
>             Project: Infrastructure
>          Issue Type: Improvement
>          Components: Confluence, JIRA, LDAP
>            Reporter: Sebb
>            Priority: Major
>
> Both JIRA and Confluence can now use LDAP for authentication.
> These system also allow non-LDAP logins.
> I assume new logins cannot be created if there is already an LDAP person with the same
id, however someone could potentially register an id which is later wanted for an ASF committer.
> To avoid this occurring, I suggest that 3rd party login names should not occupy the same
namespace. e.g. insist that such names include characters that are not permitted in LDAP names
(_,- \@ etc)



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

Mime
View raw message