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

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

Sebb commented on INFRA-18474:
------------------------------

Maybe it needs to be fed back to Atlassian, so all their customers can benefit from the solution?

> 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