On 07/13/2012 04:00 PM, Rob Crittenden wrote:
> Martin Kosek wrote:
>> On 07/12/2012 07:46 AM, Martin Kosek wrote:
>>> On 07/11/2012 09:27 PM, Rob Crittenden wrote:
Martin Kosek wrote:
> IPA 3.0 introduced range ID objects in replicated space which specify
> a range of IDs assigned via
Martin Kosek wrote:
On 07/12/2012 07:46 AM, Martin Kosek wrote:
On 07/11/2012 09:27 PM, Rob Crittenden wrote:
Martin Kosek wrote:
IPA 3.0 introduced range ID objects in replicated space which specify
a range of IDs assigned via DNA plugin. ipa-ldap-updater generates the
default ID range which
On 07/12/2012 07:46 AM, Martin Kosek wrote:
> On 07/11/2012 09:27 PM, Rob Crittenden wrote:
>> Martin Kosek wrote:
>>> IPA 3.0 introduced range ID objects in replicated space which specify
>>> a range of IDs assigned via DNA plugin. ipa-ldap-updater generates the
>>> default ID range which should c
On 07/11/2012 09:27 PM, Rob Crittenden wrote:
> Martin Kosek wrote:
>> IPA 3.0 introduced range ID objects in replicated space which specify
>> a range of IDs assigned via DNA plugin. ipa-ldap-updater generates the
>> default ID range which should correspond with IDs assigned to IPA
>> users.
>>
>>
Martin Kosek wrote:
IPA 3.0 introduced range ID objects in replicated space which specify
a range of IDs assigned via DNA plugin. ipa-ldap-updater generates the
default ID range which should correspond with IDs assigned to IPA
users.
However, since correct range size is not known, we should at l
IPA 3.0 introduced range ID objects in replicated space which specify
a range of IDs assigned via DNA plugin. ipa-ldap-updater generates the
default ID range which should correspond with IDs assigned to IPA
users.
However, since correct range size is not known, we should at least
warn that a range