Uploaded image for project: 'Confluence Data Center'
  1. Confluence Data Center
  2. CONFSERVER-5305

Non-existent users in groups cause problems when using LDAP

      If an LDAP group contains a member which doesn't exist, Confluence gets the name from the group, gets a user (which returns null) and then does things with the null pointer, rather than reporting that the group contains a user which doesn't exist (it does log it, but not in a clear way)

            [CONFSERVER-5305] Non-existent users in groups cause problems when using LDAP

            Matt Ryall added a comment -

            You're right. This issue was known but not documented anywhere.

            I've raised CONF-5723 to track it. Please add your vote there.

            Matt Ryall added a comment - You're right. This issue was known but not documented anywhere. I've raised CONF-5723 to track it. Please add your vote there.

            Please decouple the Attribute used for the login name from the group search filter.
            The attribute used for login is not necessarily the same as the member attribute of the group.
            This is especially the case with MS AD, where the loginname would be the sAMaccountName attribute of the User, while the member attribute of AD groups contains the users full DN.
            As of now, there is no meaningful use of LDAP integration with AD.

            Wolfram Richter added a comment - Please decouple the Attribute used for the login name from the group search filter. The attribute used for login is not necessarily the same as the member attribute of the group. This is especially the case with MS AD, where the loginname would be the sAMaccountName attribute of the User, while the member attribute of AD groups contains the users full DN. As of now, there is no meaningful use of LDAP integration with AD.

              Unassigned Unassigned
              tom@atlassian.com Tom Davies
              Affected customers:
              2 This affects my team
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: