-
Bug
-
Resolution: Cannot Reproduce
-
Low
-
None
-
5.4.3
-
1
-
Severity 2 - Major
-
2
-
Issue Summary
The customer is importing data from the Microsoft Active Directory group. When the member attribute in the group is more than 1500, the value is set to null. Whereas values less than 1500 are working without any issues.
Per Microsoft Documentation: https://docs.microsoft.com/en-gb/previous-versions/windows/desktop/ldap/searching-using-range-retrieval?redirectedfrom=MSDN , the range is introduced by the Active Directory server which is causing the issue.
Currently, Assets import doesn't support pagination due to which the values are set to null if the group is having more than 1500.
This is reproducible on Data Center: Yes
Steps to Reproduce
- Configure Assets Import with Active Directory
- In the Active Directory, Create groups with member attribute having more than 1500 values
- Try to synchronize and check the member attribute value in Assets.
Expected Results
Member attribute in the respective Assets Object should have all the values available in Active Directory
Actual Results
Member attribute in the respective Assets Object doesn't have any values.
The below exception is thrown in the xxxxxxx.log file:
CN=GG-MFA-ENF-CONWW1,OU=Groups,DC=corp,DC=oftest,DC=it, whenchanged=whenChanged: 20230324103356.0Z, whencreated=whenCreated: 20230324102640.0Z, objectguid=objectGUID: [B@7e8bc4bd, usnchanged=uSNChanged: 81643, usncreated=uSNCreated: 56154, objectsid=objectSid: [B@80f070f, member;range=0-1499=member;range=0-1499:
Workaround
Currently, there is no known workaround for this behavior. A workaround will be added here when available
[JSDSERVER-12865] Assets Import doesn't synchronise AD group member attribute values greater than 1500
| Assignee | New: Tripta Kaur [ 399904f8a539 ] |
| Resolution | New: Cannot Reproduce [ 5 ] | |
| Status | Original: Short Term Backlog [ 12074 ] | New: Closed [ 6 ] |
Hi everyone,
This is Ish from the JSM team. Thank you for raising this bug and bringing it to our attention. After our investigation into this issue, our engineers weren’t able to reproduce the behaviour with the classic LDAP import setup within our instances. We would like to get to the root cause of what you’re experiencing.
Could you provide exact replication steps for this issue? Further details on what your import configuration looked like, especially filters and the AD group mapping would be helpful.
If you need any assistance please contact our support team at https://support.atlassian.com/contact
Best,
Ish
Jira Service Management Team
| Labels | Original: lts10 | New: lts10nth |
| Labels | Original: lts10 lts10nth | New: lts10 |
| Sprint | New: LTS Sprint [ 7234 ] |
| Labels | Original: lts10 | New: lts10 lts10nth |
| Labels | New: lts10 |
| Remote Link | New: This issue links to "Page (Confluence)" [ 926101 ] |
We are closing the bug because we have not been able to reproduce it. If you are impacted by this issue, please reach out to support with steps on how to reproduce this.