#51115 Add samba schema by default
Closed: wontfix 3 years ago by firstyear. Opened 3 years ago by firstyear.

Issue Description

Samba can use ldap as a password provider, and to do this it requires some schema loaded. We should ship this by default as it opens up some integrations that are attractive to some deployments.


389-ds already ships two Samba schema files, 60samba3.ldif and 60samba.ldif. Which one you want to make default?

FreeIPA installs 60samba.ldif by default but doesn't use it itself.

60samba3.ldif. It doesn't conflict to 60samba.ldif, so it's not going to be a problem for you.

Metadata Update from @firstyear:
- Custom field origin adjusted to None
- Custom field reviewstatus adjusted to None

3 years ago

It looks like 60samba.ldif is broken anyway, so I don't know how you are able to use this file. 60samba3.ldif is just fine. I'll submit a fix for 60samba.ldif anyway.

[28/May/2020:11:05:58.801499700 +1000] - ERR - dse_read_one_file - The entry cn=schema in file /opt/dirsrv/etc/dirsrv/slapd-localhost/schema/60samba.ldif (lineno: 1) is invalid, error code 21 (Invalid syntax) - object class ( 1.3.6.1.4.1.7165.2.2.3 NAME 'sambaAccount' DESC 'Samba Auxilary Account' SUP top AUXILIARY MUST ( uid $ rid ): Failed to parse objectclass, error(4) at (end of input)

Either way, when fixed, they don't conflict.

We have own copy of 60samba.ldif in FreeIPA tree, that one is not broken, for sure. Thank you for checking!

Metadata Update from @firstyear:
- Issue close_status updated to: fixed
- Issue status updated to: Closed (was: Open)

3 years ago

389-ds-base is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in 389-ds-base's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/389ds/389-ds-base/issues/4168

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Metadata Update from @spichugi:
- Issue close_status updated to: wontfix (was: fixed)

3 years ago

Login to comment on this ticket.

Metadata