Description of problem:
In larger, more complex IPA environments where Replica's are not all interconnected, we are missing some dirsrv dna plugin configurations to allow a directory server to lookup ranges on other servers once exhausted.
Per bug#971111 under comment 7:
We need IPA servers to support the following:
dnaRemoteBindMethod (SIMPLE, SSL, SASL/DIGEST-MD5, or SASL/GSSAPI)
dnaRemoteConnProtocol: (LDAP, TLS, or SSL)
The 389 Devs can provide more details there.
If we do not have this, we can see problems adding users/groups once the uid/gid range is exhausted. This allows an IPA server to get a UID/GID from a server with an available range. Bug #971111 covers the DS side of the fix needed to support this configuration.
Version-Release number of selected component (if applicable):
seen often (but not always) in automated testing.
Steps to Reproduce:
1. setup IPA env m1-m2-m3
2. add user on m3
ipa: ERROR: Operations error: Allocation of a new value for range cn=posix ids,cn=distributed numeric assignment plugin,cn=plugins,cn=config failed! Unable to proceed.
user successfully added to ipa
FYI, a link to the 389 project page covering the DNA Plugin configuration:
To manually configure the DNA Plugin remote support, all shared DNA plugin configuration need to be updated:
dnaRemoteBindDN and dnaRemoteBindCred do not need to be configured in the DNA plugin configuration as we are authenticating via GSSAPI and thus do not need there options.
Second step is to authorize the replica that is not a direct replication peer of IPA master to perform the remote DNA call. Replica LDAP service DN needs to be added to nsDS5ReplicaBindDN on the remote IPA master replica configuration (cn=replica,cn=<suffix>,cn=mapping tree,cn=config) so that the IPA master can allow the operation. In order to be able to automate this step, 389-ds-base Bug 1052754 needs to be implemented first.
(In reply to Martin Kosek from comment #5)
> dnaRemoteConnProtocol: TLS
> dnaRemoteBindMethod: SASL/GSSAPI
As Simo advised, dnaRemoteConnProtocol can be set to plain "LDAP" as with "SASL/GSSAPI" one gets the encryption for free.
The ticket was postponed upstream to the next release, see the details in
The RHEL work will be therefore postponed too. Sorry for the inconvenience.
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see firstname.lastname@example.org with any questions
Created attachment 1202450 [details]
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.