FreeIPA-users June 2024

freeipa-users@lists.fedorahosted.org

27 participants
49 discussions

FreeIPA 4.11.2
by Antonio Torres 10 Jun '24

10 Jun '24

The FreeIPA team would like to announce FreeIPA 4.11.2 release! It can be downloaded from http://www.freeipa.org/page/Downloads. Builds for Fedora distributions will be available from the official repository soon. Full release notes are available at: https://www.freeipa.org/release-notes/4-11-2.html

1 0

[SSSD] Announcing SSSD 2.10.0-beta1
by Pavel Březina 07 Jun '24

07 Jun '24

# SSSD 2.10.0-beta1 The SSSD team is announcing the release of version 2.10.0-beta1 of the System Security Services Daemon. The tarball can be downloaded from: https://github.com/SSSD/sssd/releases/tag/2.10.0-beta1 See the full release notes at: https://sssd.io/release-notes/sssd-2.10.0-beta1.html RPM packages will be made available for Fedora shortly. ## Feedback Please provide comments, bugs and other feedback via the sssd-devel or sssd-users mailing lists: https://lists.fedorahosted.org/mailman/listinfo/sssd-devel https://lists.fedorahosted.org/mailman/listinfo/sssd-users # SSSD 2.10-beta1 Release Notes ## Highlights ### General information * **IMPORTANT note for downstream maintainers!** This release features significant improvements of "running with less privileges (under unprivileged service user)" feature. There is still a `./configure` option `--with-sssd-user=` available that allows downstream package maintainers to choose if support of non-root service user should be built. In case such support is built, a preferred way to configure service user is simply by starting SSSD under this user; for example, using `User=/Group=` options of systemd sssd.service file. Upstream defaults are to build `--with-sssd-user=sssd` and to install systemd service with `User=/Group=sssd`. In this case, only several helper processes - `ldap_child`, `krb5_child` and `selinux_child` - are executed with elevated capabilities (that are now granted using fine grained file capabilities instead of SUID bit). All other SSSD components run without any capabilities. In this scenario it's still possible to re-configure SSSD to run under `root` (if needed for some reason): besides changing `User/Group=` options, some other tweaks of systemd service files are required. A legacy method to configure a service user - sssd.conf `user` option - is now deprecated and its support isn’t built by default. It can be enabled using `--with-conf-service-user-support` `./configure` option if needed (for example, due to backward compatibility requirements of stable releases). Further, no matter if SSSD is built `--with-sssd-user=sssd` or `--with-sssd-user=root`, when it's configured to run under `root` (in both cases) it still runs without capabilities, the same way as when it's configured to run under `sssd` user. The only difference is from the DAC perspective. Important note: owner of `/etc/sssd/sssd.conf` file (and snippets) should match the user configured to start SSSD service. Upstream spec file changes ownership of existing `sssd.conf` to `sssd` during package installation for seamless upgrades. Additionally, this release fixes a large number of issues with "socket activation of responders" feature, making it operable out-of-the-box when the package is built `--with-sssd-user=sssd`. Please take a note, that user configured to run main sssd.service and socket activated responders (if used) should match (i.e. if sssd.service is re-configured from upstream defaults to `root` then responders services also should be re-configured). Downstream package maintainers are advised to carefully inspect changes in `contrib/sssd.spec.in`, `src/sysv/systemd/*` and `./configure` options that this release brings! * sssctl `cache-upgrade` command was removed. SSSD performs automatic upgrades at startup when needed. * Support of `enumeration` feature (i.e. ability to list all users/groups using `getent passwd/group` without argument) for AD/IPA providers is deprecated and might be removed in further releases. Those who are interested to keep using it awhile should configure its build explicitly using `--with-extended-enumeration-support` ./configure option. ### New features * The new tool `sss_ssh_knownhosts` can be used with ssh's KnownHostsCommand configuration option to retrieve the host's public keys from a remote server (FreeIPA, LDAP, etc.). This new tool, which is more reliable, replaces `sss_ssh_knownhostsproxy`. Please consider switching to using the new tool as the old one will be removed. ### Packaging changes * Building SSSD now unconditionally requires availability of `ucred`/ `SO_PEERCRED` to enforce certain security checks at runtime (see `man 7 unix` for details). * SSSD now requires `libini` not older than v1.3 * Explicit `--with-semanage` ./configure switch was removed, going forward `--with-selinux` includes this. ### Configuration changes * Default `ldap_id_use_start_tls` value changed from `false` to `true` for improved security. * Added a `ldap_use_ppolicy` option for backends with broken ppolicy extension handling. * Obsolete `config_file_version` option was removed.

1 1

ipa host-add one time password validity period?
by Masanari Iida 07 Jun '24

07 Jun '24

" ipa host-add hostname -random " create a random one time password for this system. My question is, is there any expiring date for this random one time password? Let's say, if the random password expires in 7 days, I should mention my co-worker to let them add the hosts within that period. So far, I don't see such limitation online manual "Add Hosts to IPA" section. Just I want to double check this with developer. Masa

2 2

Is there a way to change a private group to a normal user group?
by Djerk Geurts 06 Jun '24

06 Jun '24

Hi all, Working on NFS access for local system accounts I found that one NFS client was only able to use a primary group to gain access to an NFS share via group privileges, and not a secondary group. But now, I’ve run into an issue where I need to grant others access to the same files, and their use of secondary group membership isn’t a problem. So now I’m considering if I can change the private group to a normal group and still have it as the primary group for the system account. I don’t want to have to change the group ownership of 10TB of files and folders again as this takes a long time. So the gid must stay ideally stay the same. Can I: Change the group type, so it shows up in the IPA GUI and add another group to it. Delete the private group and recreate it as a normal group with the same gid and name? Or am I screwed and need to remove the user and group and recreate them from scratch? Thanks, Djerk Geurts

2 4

Setting up FreeIPA to work with Windows and other Linux Boxes
by Duncan Small 05 Jun '24

05 Jun '24

I am attempting to follow this guide (https://www.rootusers.com/how-to-login-to-windows-with-a-freeipa-account/) to add a windows box to my cluster of FreeIPA-managed linux (rhel 8/9 and ubuntu) boxes. I have gotten to the point where I have a user account on the windows box connected to FreeIPA, I change the password (since it always starts expired) but then I am hit with this error: “To sign in remotely, you need the right to sign in through Remote Desktop Services. By default, members of the Remote Desktop Users group have this right. If the group you’re in doesn’t have this right, or if the right has been removed from the Remote Desktop Users group, you need to be granted this right manually.” My user account is in the "Remote Desktop Users" and I have verified that this group has the correct permissions to allow logon via RDP (as well as verifying that no user groups are denied from logging onto the box). I also added the user to the Remote Desktop Services group policy, but that did not work. I am able to RDP in as Administrator, so I tried adding the user to Administrator just to ensure it had the right permissions, but that did not work. I have been able to replicate this behavior with a fresh box and different FreeIPA accounts. Any help, advice, or resources would be greatly appreciated. TIA

2 2

Setting up FreeIPA to work with Windows and other Linux Boxes
by Duncan Small 05 Jun '24

05 Jun '24

1 0

pki-tomcatd service stopped
by Natxo Asenjo 05 Jun '24

05 Jun '24

hi, after a botched update (https://access.redhat.com/solutions/7065748) and rolling back the changes, this service will not start: # ipactl status Directory Service: RUNNING krb5kdc Service: RUNNING kadmin Service: RUNNING named Service: RUNNING httpd Service: RUNNING ipa-custodia Service: RUNNING pki-tomcatd Service: STOPPED smb Service: RUNNING winbind Service: RUNNING ipa-otpd Service: RUNNING ipa-dnskeysyncd Service: RUNNING 1 service(s) are not running in journalctl I found this stdout/stderr messages: May 24 11:40:35 kdc1.sub.domain.tld named[27437]: zone sub.domain.tld/IN: sending notifies (serial 1716543629) May 24 11:40:35 kdc1.sub.domain.tld pki-server[27758]: ERROR: Unable to parse version number: "11.5.0" May 24 11:40:35 kdc1.sub.domain.tld pki-server[27758]: Traceback (most recent call last): May 24 11:40:35 kdc1.sub.domain.tld pki-server[27758]: File "/usr/lib/python3.9/site-packages/pki/server/pkiserver.py", line 41, in <module> May 24 11:40:35 kdc1.sub.domain.tld pki-server[27758]: cli.execute(sys.argv) May 24 11:40:35 kdc1.sub.domain.tld pki-server[27758]: File "/usr/lib/python3.9/site-packages/pki/server/cli/__init__.py", line 145, in execute May 24 11:40:35 kdc1.sub.domain.tld pki-server[27758]: super().execute(args) May 24 11:40:35 kdc1.sub.domain.tld pki-server[27758]: File "/usr/lib/python3.9/site-packages/pki/cli/__init__.py", line 217, in execute May 24 11:40:35 kdc1.sub.domain.tld pki-server[27758]: module.execute(module_args) May 24 11:40:35 kdc1.sub.domain.tld pki-server[27758]: File "/usr/lib/python3.9/site-packages/pki/server/cli/upgrade.py", line 144, in execute May 24 11:40:35 kdc1.sub.domain.tld pki-server[27758]: self.upgrade( May 24 11:40:35 kdc1.sub.domain.tld pki-server[27758]: File "/usr/lib/python3.9/site-packages/pki/server/cli/upgrade.py", line 178, in upgrade May 24 11:40:35 kdc1.sub.domain.tld pki-server[27758]: upgrader.upgrade() May 24 11:40:35 kdc1.sub.domain.tld pki-server[27758]: File "/usr/lib/python3.9/site-packages/pki/upgrade.py", line 481, in upgrade May 24 11:40:35 kdc1.sub.domain.tld pki-server[27758]: versions = self.versions() May 24 11:40:35 kdc1.sub.domain.tld pki-server[27758]: File "/usr/lib/python3.9/site-packages/pki/upgrade.py", line 238, in versions May 24 11:40:35 kdc1.sub.domain.tld pki-server[27758]: current_version = self.get_current_version() May 24 11:40:35 kdc1.sub.domain.tld pki-server[27758]: File "/usr/lib/python3.9/site-packages/pki/upgrade.py", line 341, in get_current_version May 24 11:40:35 kdc1.sub.domain.tld pki-server[27758]: current_version = self.get_tracker().get_version() May 24 11:40:35 kdc1.sub.domain.tld pki-server[27758]: File "/usr/lib/python3.9/site-packages/pki/upgrade.py", line 141, in get_version May 24 11:40:35 kdc1.sub.domain.tld pki-server[27758]: return pki.util.Version(version) May 24 11:40:35 kdc1.sub.domain.tld pki-server[27758]: File "/usr/lib/python3.9/site-packages/pki/util.py", line 613, in __init__ May 24 11:40:35 kdc1.sub.domain.tld pki-server[27758]: raise Exception('Unable to parse version number: %s' % obj) May 24 11:40:35 kdc1.sub.domain.tld pki-server[27758]: Exception: Unable to parse version number: "11.5.0" May 24 11:40:35 kdc1.sub.domain.tld systemd[1]: pki-tomcatd(a)pki-tomcat.service: Control process exited, code=exited, status=1/FAILURE May 24 11:40:35 kdc1.sub.domain.tld systemd[1]: pki-tomcatd(a)pki-tomcat.service: Failed with result 'exit-code'. May 24 11:40:35 kdc1.sub.domain.tld systemd[1]: Failed to start PKI Tomcat Server pki-tomcat. So it seems something is broken on this upgrade script. This is in in almalinux 9.3 ipa-server-4.10.2-5.el9_3.alma.1.x86_64 I cannot upgrade because I get bitten by the named ldap thing, even though the versions are newer. I will create a replicat to a rhel host but first I need to get the CA up and running obviously :-). Any ideas? Thanks! -- regards, natxo -- -- Groeten, natxo

3 11

kpi-tomcatd failing to start
by girish f 03 Jun '24

03 Jun '24

I have IPA setup long back. Some of the certificates expired. So i went back in time and then it's working super smooth. When i did ipa-cert-fix --> error is Server-Cert not found I renewed kerberos kdc.key kdc.crt. But still it's failing to start the kpi_tomcatd. When i check status of kpi-tomcatd@kpi-tomcatd it shows running, but service starts to fail when i come back to current time and restart ipactl restart. need urgent help please

3 7

Remove bad replica nodes from list
by Satish Patel 03 Jun '24

03 Jun '24

Folks, I am trying to build some replicas and somehow they failed but because they are half baked they are stuck in master nodes and not letting me remove them. I have tried all the options and don't know how to get rid of them. I want to remove ldap-vx-010103-1.site5.example.com and ldap-vx-010103-2.site5.example.com. I have removed them from topology and from host and hostgroup ipaservers list but no luck. I have totally shut down replicas nodes but still no luck. Are there any good ways to clean them up? [root@ldap-vx-010101-4 ~]# ipa-replica-manage list -v `hostname` ldap-vx-010101-1.site5.example.com: replica last init status: None last init ended: 1970-01-01 00:00:00+00:00 last update status: Error (0) Replica acquired successfully: Incremental update succeeded last update ended: 2024-05-16 01:58:02+00:00 ldap-vx-010101-2.site5.example.com: replica last init status: None last init ended: 1970-01-01 00:00:00+00:00 last update status: Error (0) Replica acquired successfully: Incremental update succeeded last update ended: 2024-05-16 01:58:02+00:00 ldap-vx-010101-3.site5.example.com: replica last init status: None last init ended: 1970-01-01 00:00:00+00:00 last update status: Error (0) Replica acquired successfully: Incremental update succeeded last update ended: 2024-05-16 01:58:02+00:00 ldap-vx-010101-5.site5.example.com: replica last init status: None last init ended: 1970-01-01 00:00:00+00:00 last update status: Error (0) Replica acquired successfully: Incremental update succeeded last update ended: 2024-05-16 01:58:02+00:00 ldap-vx-010103-1.site5.example.com: replica last init status: Error (0) last init ended: 1970-01-01 00:00:00+00:00 last update status: Error (-1) Problem connecting to replica - LDAP error: Can't contact LDAP server (connection error) last update ended: 2024-05-11 10:30:33+00:00 ldap-vx-010103-2.site5.example.com: replica last init status: Error (0) Total update succeeded last init ended: 2024-05-10 20:35:02+00:00 last update status: Error (-1) Problem connecting to replica - LDAP error: Can't contact LDAP server (connection error) last update ended: 1970-01-01 00:00:00+00:00 ldap-vx-010103-3.site5.example.com: replica last init status: Error (0) Total update succeeded last init ended: 2024-05-10 21:14:53+00:00 last update status: Error (0) Replica acquired successfully: Incremental update succeeded last update ended: 2024-05-16 01:58:02+00:00

2 4

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

FreeIPA-users June 2024