Bug 33340 – univention-ad-takeover - count_ad_object_numbers is limited to 1000 entries (MaxPageSize)

Bug 33340 - univention-ad-takeover - count_ad_object_numbers is limited to 1000 entries (MaxPageSize)


Summary:	univention-ad-takeover - count_ad_object_numbers is limited to 1000 entries (...

Status:	RESOLVED WONTFIX

Product:	UCS
Classification:	Unclassified
Component:	AD Connector
Version:	UCS 4.2
Hardware:	Other Linux

Importance:	P5 normal (vote)
Target Milestone:	---
Assigned To:	Samba maintainers
QA Contact:

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2013-11-12 17:27 CET by Felix Botner
Modified:	2020-07-03 20:54 CEST (History)
CC List:	2 users (show)

See Also:
What kind of report is it?:	Bug Report
What type of bug is this?:	3: Simply Wrong: The implementation doesn't match the docu
Who will be affected by this bug?:	1: Will affect a very few installed domains
How will those affected feel about the bug?:	1: Nuisance – not a big deal but noticeable
User Pain:	0.017
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):	Workaround is available
Max CVSS v3 score:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Felix Botner

2013-11-12 17:27:10 CET

I have a Windows ad with 1500 users, but univention-ad-takeover prints the following warning:

Found 997 user objects on the remote server.
Number of user objects after takeover would be 1000. This would exceed the number of licensed objects (5).

univention-ad-takeover finds max 1000 entries in count_ad_object_numbers() because of "PAGE_SIZE = 1000" (MaxPageSize limitation in Windows AD).

So this warning is a little bit confusing. 

The actual takeover migrates all 1500 users to ucs.

Comment 1 Stefan Gohmann

2016-10-05 14:48:16 CEST

Workaround is to increase the PAGE_SIZE on AD side.

Comment 2 Stefan Gohmann

2017-06-16 20:40:13 CEST

This issue has been filed against UCS 3. UCS 3 is out of the normal maintenance and many UCS components have vastly changed in UCS 4.

If this issue is still valid, please change the version to a newer UCS version otherwise this issue will be automatically closed in the next weeks.

Comment 3 Ingo Steuwer

2020-07-03 20:54:27 CEST

This issue has been filed against UCS 4.2.

UCS 4.2 is out of maintenance and many UCS components have changed in later releases. Thus, this issue is now being closed.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or reopen it and update the UCS version. In this case please provide detailed information on how this issue is affecting you.