Learn more about these different git repos.
Other Git URLs
In ticket #1031, Ondrej Valousek proposed to add this mapping to the Active Directory schema for the autofs map and key maps:
ldap_autofs_map_object_class = nisMap ldap_autofs_entry_object_class = nisObject ldap_autofs_map_name = nisMapName ldap_autofs_entry_value = nisMapEntry
We should research whether this is the standard mapping in AD world for autofs maps and if so, add the maps.
Ondrej, do you maybe have a pointer to any documentation that describes the mappings?
cc: => ondrejv
Fields changed
milestone: NEEDS_TRIAGE => SSSD AD Extensions Feature
rhbz: => 0
Replying to [comment:1 jhrozek]:
Ondrej, do you maybe have a pointer to any documentation that describes the mappings? Well, I do not have any documentation. The only thing I know is that:
Ondrej
component: SSSD => AD Provider milestone: SSSD AD Extensions Feature => SSSD 1.9.0 beta 5
Active Directory does not appear to have a mechanism for configuring automount maps through their standard admin console. Since this implies that any automount configuration added would have to be custom, I don't really see a value in changing our defaults right now to match one possible configuration.
If Active Directory in the future adopts a standard implementation, we can implement this at that time.
Moving to NEEDS_TRIAGE for re-evaluation.
milestone: SSSD 1.9.0 beta 5 => NEEDS_TRIAGE
AD does not have a standard mechanism to map to so we are closing this ticket.
milestone: NEEDS_TRIAGE => SSSD 1.9.0 resolution: => wontfix status: new => closed
If Active Directory in the future adopts a standard implementation, we can implement this at that time. Note that RFC3207 IS a standard. The fact that sssd only counts on RFC2307bis is something else. Even automounter itself supports both standards - it tries RFC2307bis first and then falls back to rfc2307. Maybe we should do the same - it would fix this problem, too.
Metadata Update from @jhrozek: - Issue set to the milestone: SSSD 1.9.0
SSSD is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in SSSD's github repository.
This issue has been cloned to Github and is available here: - https://github.com/SSSD/sssd/issues/2383
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Login to comment on this ticket.