Previously, we were failing to start if ldap_idmap_autorid_compat was True but the default domain SID was unspecified. This is the recommended configuration, but it is functional without it. There is just a slight risk that the IDs will be inconsistent between machines if the first user requested is not from the default domain.
On 09/21/2012 10:19 AM, Stephen Gallagher wrote:
Previously, we were failing to start if ldap_idmap_autorid_compat was True but the default domain SID was unspecified. This is the recommended configuration, but it is functional without it. There is just a slight risk that the IDs will be inconsistent between machines if the first user requested is not from the default domain.
Sent the wrong version of the patch. The attached version has a better warning message.
On Fri, Sep 21, 2012 at 11:12:37AM -0400, Stephen Gallagher wrote:
On 09/21/2012 10:19 AM, Stephen Gallagher wrote:
Previously, we were failing to start if ldap_idmap_autorid_compat was True but the default domain SID was unspecified. This is the recommended configuration, but it is functional without it. There is just a slight risk that the IDs will be inconsistent between machines if the first user requested is not from the default domain.
Sent the wrong version of the patch. The attached version has a better warning message.
Ack
On Mon, Sep 24, 2012 at 01:04:30PM +0200, Jakub Hrozek wrote:
On Fri, Sep 21, 2012 at 11:12:37AM -0400, Stephen Gallagher wrote:
On 09/21/2012 10:19 AM, Stephen Gallagher wrote:
Previously, we were failing to start if ldap_idmap_autorid_compat was True but the default domain SID was unspecified. This is the recommended configuration, but it is functional without it. There is just a slight risk that the IDs will be inconsistent between machines if the first user requested is not from the default domain.
Sent the wrong version of the patch. The attached version has a better warning message.
Ack
Pushed to master.
sssd-devel@lists.fedorahosted.org