Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[RFE] Unable to use AD provider for automount lookups #2674

Closed
sssd-bot opened this issue May 2, 2020 · 0 comments
Closed

[RFE] Unable to use AD provider for automount lookups #2674

sssd-bot opened this issue May 2, 2020 · 0 comments
Labels
Bugzilla Closed: Fixed Issue was closed as fixed.

Comments

@sssd-bot
Copy link

sssd-bot commented May 2, 2020

Cloned from Pagure issue: https://pagure.io/SSSD/sssd/issue/1632


https://bugzilla.redhat.com/show_bug.cgi?id=874985 (Red Hat Enterprise Linux 6)

Description of problem:
I am unable to use AD provider for autofs map storage as of sssd version 1.9.2.
Looks like 'ad' provider is supported for everthing but autofs.

Ondrej

Comments


Comment from dpal at 2012-11-15 15:55:30

We can provide instruction and workaround in a release note if needed.

blockedby: =>
blocking: =>
coverity: =>
design: =>
design_review: => 0
feature_milestone: =>
fedora_test_page: =>
milestone: NEEDS_TRIAGE => SSSD 1.10 beta
summary: Unable to use AD provider for automount lookups => [RFE] Unable to use AD provider for automount lookups
testsupdated: => 0
type: defect => enhancement


Comment from dpal at 2012-12-20 22:03:42

Fields changed

selected: => May


Comment from dpal at 2013-03-16 01:19:56

Fields changed

review: => 1


Comment from jhrozek at 2013-04-04 15:46:31

Fields changed

priority: major => minor


Comment from dpal at 2013-05-13 15:28:24

Fields changed

milestone: SSSD 1.10 beta => SSSD 1.12 beta


Comment from jhrozek at 2013-09-12 10:30:21

When designing this feature, we could use the value of homeDirectory to autogenerate the map. This would help the situation where the Windows admins don't want to populate any data outside what's needed for Windows clients.

Needs design.

changelog: =>


Comment from jhrozek at 2015-11-11 17:38:32

Linked to Bugzilla bug: https://bugzilla.redhat.com/show_bug.cgi?id=1278694 (Red Hat Enterprise Linux 6)

rhbz: [https://bugzilla.redhat.com/show_bug.cgi?id=874985 874985] => [https://bugzilla.redhat.com/show_bug.cgi?id=874985 874985], [https://bugzilla.redhat.com/show_bug.cgi?id=1278694 1278694]


Comment from jhrozek at 2015-11-19 12:12:04

This code works for me: jhrozek@feb0d46

I wrote the provider even if it wasn't planned for the next version. It turned out to be easy task and would allow to close other tickets that would otherwise be hard to fix (#2862).

mark: => 0
sensitive: => 0


Comment from jhrozek at 2015-11-19 12:13:06

Fields changed

cc: => ondrejv2


Comment from jhrozek at 2015-11-23 11:50:04

Fields changed

patch: 0 => 1


Comment from jhrozek at 2015-11-26 17:01:47

Fields changed

milestone: SSSD 1.14 beta => SSSD 1.14 alpha


Comment from jhrozek at 2015-11-27 09:48:05

There is a typo we need to fix in the man page, I'll close the ticket when we do.


Comment from jhrozek at 2015-12-10 11:42:01

Also pushed to sssd-1-13: fee0024

milestone: SSSD 1.14 alpha => SSSD 1.13.3
resolution: => fixed
status: new => closed


Comment from jhrozek at 2017-02-24 14:50:55

Metadata Update from @jhrozek:

  • Issue set to the milestone: SSSD 1.13.3
@sssd-bot sssd-bot added Bugzilla Closed: Fixed Issue was closed as fixed. labels May 2, 2020
@sssd-bot sssd-bot closed this as completed May 2, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bugzilla Closed: Fixed Issue was closed as fixed.
Projects
None yet
Development

No branches or pull requests

1 participant