Learn more about these different git repos.
Other Git URLs
In an IRC discussion with Jakub about autofs he suggested I add ipa_automount_location inside my IPA provider. That worked fine and autofs seemed to function.
I'm unable to do the same using the SSSDConfig python interface, I get:
NoOptionError: Section [example.com] has no option [ipa_automount_location]
I tried fetching the autofs service and updating that but I get the same error:
NoOptionError: Section [autofs] has no option [ipa_automount_location]
sssd-1.8.92-0.20120524T1212Zgitde00277.fc17
It works for me when I set up autofs_provider=ipa in the config file.
autofs_provider=ipa
By the way, the default automounter location is called default, which is IIRC created automatically on the IPA server, so unless you are overriding the location to a custom one, you should be fine with the defaults.
default
Did you find you need to change the defaults?
I wanted to use a custom location. Both need to be supported.
Confirmed that setting the autofs provider lets me set the location.
I'm wondering whether we should special-case the IPA provider in the configAPI.
Currently, only options for the providers that are explicitly set (as was the case with explicitly setting autofs_provider=ipa) can be read in the configAPI, see SSSDDomain.list_options_with_mandatory
SSSDDomain.list_options_with_mandatory
This will be addressed later as a part of #1308.
milestone: NEEDS_TRIAGE => SSSD Deferred resolution: => duplicate rhbz: => 0 status: new => closed
misconfiguration with use of sssd API from Rob : Closing duplicate of ticket 1308 : will be solved by having single provider = ... which would set all id, auth, access .. etc providers automatically
Metadata Update from @rcritten: - Issue set to the milestone: SSSD Patches welcome
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/2405
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.