#693 closed enhancement (fixed)

Add warning about Active Directory shouldn't be enabled if not using CIFS

Reported by: delphij Owned by:
Priority: trivial Milestone:
Component: Backend Version: 8.0-RELEASE
Keywords: Cc:

Description

Just keep a memo here so we won't forget to fix this (maybe by collapsing LDAP and AD configuration into Samba's?)

14:03 < bmilman> request that there be a graphical warning when someone tries to enable AD without CIFS

Change History (3)

comment:1 follow-up: Changed 22 months ago by gcooper

That's not entirely true. Adding AD login support via PAM is a very worthy enhancement that I think we should pursue to improve usability and reduce authentication headaches when authentication data goes out of sync.

comment:2 in reply to: ↑ 1 ; follow-up: Changed 22 months ago by delphij

Replying to gcooper:

That's not entirely true. Adding AD login support via PAM is a very worthy enhancement that I think we should pursue to improve usability and reduce authentication headaches when authentication data goes out of sync.

The real problem here is that in order to enable Active Directory in the current setup, one has to enable CIFS in the first place, as it rely on several services that Samba provides.

comment:3 in reply to: ↑ 2 Changed 15 months ago by jhixson

  • Resolution set to fixed
  • Status changed from new to closed

Replying to delphij:

Replying to gcooper:

That's not entirely true. Adding AD login support via PAM is a very worthy enhancement that I think we should pursue to improve usability and reduce authentication headaches when authentication data goes out of sync.

The real problem here is that in order to enable Active Directory in the current setup, one has to enable CIFS in the first place, as it rely on several services that Samba provides.

Thanks to gcooper, some time ago, this is no longer the case. CIFS no longer needs to be enabled for AD to work.

Note: See TracTickets for help on using tickets.