Uploaded image for project: 'Crowd Data Center'
  1. Crowd Data Center
  2. CWD-2441

Use sAMAccountName attribute for group name by default when using Active Directory

    • Icon: Suggestion Suggestion
    • Resolution: Timed out
    • None
    • None
    • None
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Currently we use cn attribute for group names, but this value is not always unique, which is a requirement for successful synchronisation. We already use sAMAccountName for user names. We also need to add a Group Name RDN attribute, and change SpringLDAPConnector#addGroup to use it when generating dn.

            [CWD-2441] Use sAMAccountName attribute for group name by default when using Active Directory

            Thank you for taking the time to file and comment on this issue. Feedback like yours helps us release valuable Crowd features that solve problems for the greater customer base. To that end, we aim to keep our issues up-to-date so that they accurately reflect current customer needs. Because there has been no customer activity on this issue in a long time, we have marked it as closed. If you still feel that this issue is still relevant to your needs, please feel free to raise a new issue and link to this one.

            If you would like to see how we select features for a new release, please read http://confluence.atlassian.com/display/DEV/Implementation+of+New+Features+Policy.

            Lukasz Pater added a comment - Thank you for taking the time to file and comment on this issue. Feedback like yours helps us release valuable Crowd features that solve problems for the greater customer base. To that end, we aim to keep our issues up-to-date so that they accurately reflect current customer needs. Because there has been no customer activity on this issue in a long time, we have marked it as closed. If you still feel that this issue is still relevant to your needs, please feel free to raise a new issue and link to this one. If you would like to see how we select features for a new release, please read http://confluence.atlassian.com/display/DEV/Implementation+of+New+Features+Policy .

            Hi Aaron,

            I have created a JIRA support ticket for you at: support.atlassian.com You should receive an email shortly containing a direct link to the support ticket.

            Please refer to the support ticket for any future correspondence relating to your issue.

            In future can you please raise support requests such as this by creating an issue in our support system, https://support.atlassian.com, not in http://jira.atlassian.com. As our support engineers respond to cases in https://support.atlassian.com, it will ensure that your problem gets addressed as quickly as possible. Also, https://support.atlassian.com is configured so that only Atlassian and you have access to the case, therefore it is a more appropriate location for us to gather any required system data and configuration from you.

            Regards

            Bogdan

            Bogdan Dziedzic [Atlassian] added a comment - Hi Aaron, I have created a JIRA support ticket for you at: support.atlassian.com You should receive an email shortly containing a direct link to the support ticket. Please refer to the support ticket for any future correspondence relating to your issue. In future can you please raise support requests such as this by creating an issue in our support system, https://support.atlassian.com , not in http://jira.atlassian.com . As our support engineers respond to cases in https://support.atlassian.com , it will ensure that your problem gets addressed as quickly as possible. Also, https://support.atlassian.com is configured so that only Atlassian and you have access to the case, therefore it is a more appropriate location for us to gather any required system data and configuration from you. Regards Bogdan

            I would like to add, if you have two different crowd directories attached to a single jira application, and there is a duplicate named user in each directory, the application will fail to sync and will never complete a user sync.

            for example:
            directory a: john.user
            directory b: john.user

            jira application contains directory a and directory b

            when jira application attempts to sync, it will throw an exception and never continue synchronization.

            2011-05-13 08:22:29,898 QuartzWorker-1 ERROR ServiceRunner     [atlassian.crowd.directory.DbCachingDirectoryPoller] Error occurred while refreshing the cache for directory [ 10200 ].
            com.atlassian.crowd.embedded.ofbiz.db.DataAccessException: org.ofbiz.core.entity.GenericEntityException: while inserting: [GenericEntity:Membership][id,3505][membershipType,GROUP_USER][lowerParentName,issuetrack-users][parentId,10238][childId,12237][childName,jon.katz][lowerChildName,jon.katz][directoryId,10200][parentName,issuetrack-users] (SQL Exception while executing the following:INSERT INTO jira.cwd_membership (ID, parent_id, child_id, membership_type, group_type, parent_name, lower_parent_name, child_name, lower_child_name, directory_id) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?) (Cannot insert duplicate key row in object 'jira.cwd_membership' with unique index 'uk_mem_parent_child_type'.))        at com.atlassian.crowd.embedded.ofbiz.db.OfBizHelper.createValue(OfBizHelper.java:167)
            

            Ex Employee Aaron Bockelie added a comment - I would like to add, if you have two different crowd directories attached to a single jira application, and there is a duplicate named user in each directory, the application will fail to sync and will never complete a user sync. for example: directory a: john.user directory b: john.user jira application contains directory a and directory b when jira application attempts to sync, it will throw an exception and never continue synchronization. 2011-05-13 08:22:29,898 QuartzWorker-1 ERROR ServiceRunner [atlassian.crowd.directory.DbCachingDirectoryPoller] Error occurred while refreshing the cache for directory [ 10200 ]. com.atlassian.crowd.embedded.ofbiz.db.DataAccessException: org.ofbiz.core.entity.GenericEntityException: while inserting: [GenericEntity:Membership][id,3505][membershipType,GROUP_USER][lowerParentName,issuetrack-users][parentId,10238][childId,12237][childName,jon.katz][lowerChildName,jon.katz][directoryId,10200][parentName,issuetrack-users] (SQL Exception while executing the following:INSERT INTO jira.cwd_membership (ID, parent_id, child_id, membership_type, group_type, parent_name, lower_parent_name, child_name, lower_child_name, directory_id) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?) (Cannot insert duplicate key row in object 'jira.cwd_membership' with unique index 'uk_mem_parent_child_type'.)) at com.atlassian.crowd.embedded.ofbiz.db.OfBizHelper.createValue(OfBizHelper.java:167)

              Unassigned Unassigned
              onevalainen Olli Nevalainen
              Votes:
              3 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved:

                  Estimated:
                  Original Estimate - 4h
                  4h
                  Remaining:
                  Remaining Estimate - 4h
                  4h
                  Logged:
                  Time Spent - Not Specified
                  Not Specified