Revision as of 23:03, 4 September 2024

IMPORTANT: The content of this section is outdated. Please update this section if you can. If you have checked or updated this section and found the content to be suitable, please remove this notice.

LDAP

Participants	Fwd
Skills	Linux, OpenLDAP, FreeRadius
Status	Finished
Niche	Software
Purpose	Infrastructure
Tool	Yes
Location
Cost
Tool category

LDAP Property "Tool Image" (as page type) with input value "File:{{{Picture}}}" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. {{{Picture}}} {{#if:Yes | [[Tool Owner::{{{ProjectParticipants}}} | }} {{#if:Yes | [[Tool Cost::{{{Cost}}} | }}

Status

Connected machines and services

Workstations

The workstations listed above are set up as follows:

Homedirs mounted over NFS from dumpster-a (except user 'printer' on PrinterPC)
Users in the LDAP 'sudo' group can sudo.
Homedirs are created on the NFS-export when adding a user to LDAP (like this)

VM's

NURDServices (only users in group "admins" can log in)
Stroopwafel (a VM for all members to irssi or other processes)

Wiki

Authentication on this wiki is done via SAML.

Limitations

The mediawiki login system converts the first character of usernames to uppercase due to restrictions on usernames. To get around this we've enabled $wgLDAPLowercaseUsernameScheme. This requires usernames to be all lowercase in the LDAP.
Users are maintained through the LDAP, so creating a user on the Wiki is no longer possible. It could be enabled, but that would require adding a user with write-access in the LDAP. That seems a little scary for now. It would however offer the possibility of changing your LDAP password through the Wiki.

Wifi (Spacenet)

The LDAP serves as a userdb for Spacenet, which is connected via FreeRADIUS. For full details see the Spacenet-page. Only users in group "spacenet" can log in.

DHCP

See the network page.

(Un)locking the front door

See Spacelock.

@@ Line 10: / Line 10: @@
 = Status =
-= Adding a new member =
-There's a guide [[Adding_a_new_member_to_the_ldap|here]] explaining the steps for adding a new member to the LDAP.
 = Connected machines and services =
@@ Line 25: / Line 23: @@
 * Users in the LDAP 'sudo' group can sudo.
 * Homedirs are created on the NFS-export when adding a user to LDAP ([http://documentation.fusiondirectory.org/en/documentation_faq/command_after like this])
-=== Setting up other workstations in this way ===
-To get this to work you need to:
-* create all local users in LDAP and then delete local users (else UIDs/GIDs get confusing)
-* move homedirs to nurdservices (fix ownership because LDAP-users have a different UID) then delete local homedirs
-* put https://www.sslcertificaten.nl/files/PositiveSSLCA2.crt in /etc/ssl/certs/ with permissions 644
-*insert into /etc/fstab:
-<code>dumpster-a.nurdspace.lan:/vol/home   /home   nfs   rw,auto,exec,vers=3   0   0</code>
-* install nfs client stuff:
-<code>apt-get install rpcbind nfs-common</code>
-* install [http://wiki.debian.org/LDAP/NSS#NSS_Setup_with_libnss-ldapd libnss-ldapd] (see below for settings asked during installation, in the selection list check passwd, group and shadow)
-* install nslcd and libpam-ldapd (see below for settings asked during installation)
-* /etc/nslcd.conf should mention at least the following:
- uri ldaps://ldap.nurdspace.nl/
- base dc=nurdspace,dc=lan
- binddn cn=read-user,ou=systems,dc=nurdspace,dc=lan
- bindpw (obtain from other machine)
- ssl on
- tls_reqcert demand
- tls_cacertfile /etc/ssl/certs/ca-certificates.crt
-* configure /etc/nsswitch.conf:
- passwd:    files ldap
- group:    files ldap
- shadow:    files ldap
-* restart nslcd
-* restart nscd
-* check if ldap users are listed when you run "getent passwd"
-* sudo might not work until you type 'id' which is [http://wiki.debian.org/LDAP/PAM kind of a mystery]
-Useful reading: http://www.debian-administration.org/article/OpenLDAP_installation_on_Debian
-In certain cases sudo can break. This can be fixed with [http://osdir.com/ml/general/2013-01/msg44182.html a patch] while it's not fixed properly.
 == VM's ==
 * [[NURDServices]] (only users in group "admins" can log in)
-* [[Egg]] (a VM for all members to irssi or other processes)
+* [[Stroopwafel]] (a VM for all members to irssi or other processes)
-== ldap.nurdspace.nl ==
-Slapd and [http://fusiondirectory.org FusionDirectory] are running on [[NURDServices]]. FusionDirectory's web interface can be accessed on https://ldap.nurdspace.nl.
 == Wiki ==
-Authentication on this wiki is done via SAML. Zarya needs to document this.
+Authentication on this wiki is done via SAML.
 === Limitations ===
@@ Line 79: / Line 40: @@
 == DHCP ==
 See the [[Network|network page]].
-= Future plans =
-The most important machines and services are now hooked up to the LDAP. However, there's always room for more.
-== More groups for different purposes ==
-We should create more groups for specific purposes, such as:
-* Workstation users (now only sudo'ers are treated separately)
-* Separate group per workstation? Or some sort of hierarchy of groups, so members need only be in 1 group?
-* <s>Spacenet users</s> done
 == (Un)locking the front door ==
 See [[Spacelock]].
-== Member registration ==
-Currently the users in group "members" are maintained by hand. A little more automation would be appropriate. Hooking it up to actual money transactions might be far-fetched, but maybe something else is possible.
-== E-mail and contacts services ==
-We could install Zimbra or Zarafa, or maybe some smaller services to provide e-mail accounts, mailinglist functionality and maybe a CardDAV services for members.
-== Make use of more of FusionDirectory's features ==
-FusionDirectory has [http://documentation.fusiondirectory.org/en/documentation/available_plugins features/plugins] for applications, mime-types, workstations, object groups, public key authentication. Maybe some of these could be useful?
-* Systems plugin installed and working, so we can now list all systems (workstations, servers) in the LDAP
-* Wake-on-lan not working yet, probably due to a bug in Argonaut. The server- and client-services see eachother but wake-on-lan commands don't come through and you get an error in the web interface:
- Communication failure with the infrastructure service:
- Error: Request error: No client module can handle action Deployment.wake for target 00:0d:56:06:b6:26
-* Maybe maintain the internal DNS with [http://documentation.fusiondirectory.org/en/documentation/plugin/dns_plugin/how_to_setup_dns_plugin_1.0.5 this plugin]?
-* The DHCP feature sucks, so it's been rolled back.
-== Wiki ==
-* Members page filled based on LDAP group 'members'.
-== Misc ==
-* Investigate possibility of moving to a different database back-end ([http://www.openldap.org/faq/data/cache/978.html back-sql])
-* Exclude weak ciphers from olcTLSCipherSuite in cn=config
-* Setting "change password on first login" in FusionDirectory doesn't get enforced through PAM
-* Upgrade FusionDirectory from 1.0.5 to [http://fusiondirectory.org/basic/press#fd-1.0.6 1.0.6]
-* Maintain [http://nurdspace.nl/Category:Members Members] page from LDAP ([http://www.mediawiki.org/wiki/Extension:External_Data#.23get_ldap_data_-_retrieve_data_from_LDAP_directory Like so], but this only displays 1 entry. Could be fixed [http://www.mediawiki.org/wiki/Extension_talk:External_Data/Archive_2012#.23for_external_table_support_for_.23get_ldap_data like so].)
-* Check if the passwordmailer on FusionDirectory works
-* Check out [http://www.lichteblau.com/ldapvi/manual/ ldapvi]