Old Home Folders and Free ipa users
by Alper AYKUT
Hello I have 5 servers. The users of all servers are created locally. All
users have Home. Now I will connect the Servers to the Free ipa server to
enable them to log in with the Users I have created in Free IPA. However,
how will the users' home folders that were created in the past match the
User created in Free ipa? Or will the users need to delete their home
folders to be created again.
If I need to delete the Home folders of the users, I will need to back up
the data of all users. This is a huge workload.
Thankyou for support.
4 months, 3 weeks
[SSSD] Announcing SSSD 2.9.4
by Pavel Březina
# SSSD 2.9.4
The SSSD team is announcing the release of version 2.9.4 of the
System Security Services Daemon. The tarball can be downloaded from:
https://github.com/SSSD/sssd/releases/tag/2.9.4
See the full release notes at:
https://sssd.io/release-notes/sssd-2.9.4.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.9.4 Release Notes
## Highlights
### Important fixes
* Fixes a crash when PAM passkey processing incorrectly handles
non-passkey data.
* A workaround was implemented to handle gracefully misbehaving
applications that destroy internal state of SSSD client librarires. A
particular example of such application is described in
https://github.com/TigerVNC/tigervnc/issues/1709.
* An error when rotating KCM's logs was fixed. When KCM's logs were
rotated by logrotate, KCM would still use the old file (renamed
sssd_kcm.log.1). Only after KCM was restarted (either manually or
automatically) the new log file would be used. This problem is now
solved and KCM uses the new file immediately.
* Fixed group membership handling when members are coming from
different forest domains and using ldap token groups is prohibited.
* Files provider was erroneously taking into consideration
`local_auth_policy` config option, thus breaking smartcard
authentication of local user in setups that didn't explicitly specify
this option. This is now fixed.
4 months, 3 weeks
Greenfield FreeIPA deployment - is it OK to put FreeIPA at the domain apex, or a "best practice" to put it in a subdomain?
by Braden McGrath
Hello FreeIPA-users. The Subject line is the core of my question here; I'll provide a bit more detail below.
I work for what is (effectively) a startup, non-profit internet provider. I have an extensive Windows background, and "know enough to be dangerous" with Linux & BSD (have been tinkering with GNU/Linux on and off since Slackware 3.0 or 3.1). I'm very familiar with Windows Active Directory, but the org does not have any AD infrastructure right now (and being nonprofit, are trying to avoid spending money for MS, especially when all of the other VMs will be Linux or BSD anyway).
Given the nonprofit nature, I discovered FreeIPA when looking for a free centralized directory system. The goal is to consolidate all credentials for *other* Linux VMs (customer-facing DNS, CRM web server, SNMP/network graphing servers, etc) as well as provide a back-end for RADIUS for management of network equipment (switches, routers, P2P wireless, etc). Simplifying DNS management and replication is also appealing, I'd rather administrate one system than two or three.
In case it changes your opinion of the plan at all - all of the network equipment and VMs will be on *private* (10.x) IPv4 space and behind one or more firewalls, at least initially. We do want to add public IPv6, but do not have that yet. We only have a small allocation (/26) of public v4 from our upstream that will be NATed through a firewall and not directly on any devices. The traffic to FreeIPA is going to be internal-only, I do not plan on exposing FreeIPA's DNS "to the world" at all. Even customer-facing internal DNS will likely be through separate caching forwarders pointing back to FreeIPA.
I have a completely unused, publicly registered domain (let's just call it "example.net" for this thread) available to dedicate to this system. We also own "example.org" and are using that for our public web presence, and I intend to keep that entirely standalone.
Given that I have no current "interoperability" concerns, is there anything "wrong" with putting FreeIPA directly at the root of example.net? Or would it be more wise, from an interop, security, or manageability standpoint (i.e. a "best practice"), to root FreeIPA at something like auth.example.net or ipa.example.net and then have a separate set of nameservers handling the base domain? If I put FreeIPA's root (and Kerberos realm) in a subdomain, is it possible to *also* have it manage the parent domain's DNS entries?
I've read through the Quick Start Guide and Deployment Recommendations (https://www.freeipa.org/page/Deployment_Recommendations), which is part of how I've come to the decisions I've made thus far. I couldn't really find guidance one way or the other on whether FreeIPA "should" be in a subdomain or not, hence this posting. I would appreciate any insight the community can provide!
4 months, 3 weeks
FreeIPA web session timeout
by Yuri Krysko
Hello,
Could you please advise how to configure FreeIPA web UI user session timeout?
Thanks,
Yuri
________________________________
LEGAL DISCLAIMER: M.C. Dean, Inc. and its subsidiaries considers this e-mail and any files transmitted with it to be protected, proprietary or privileged information intended solely for the use of the named recipient(s). Any disclosure of this material or the information contained herein, in whole or in part, to anyone outside of the intended recipient or affiliates is strictly prohibited. M. C. Dean, Inc. accepts no liability for the content of this e-mail or for the consequences of any actions taken on the basis of the information contained in it, unless that information is subsequently confirmed in writing. Employees of M.C. Dean, Inc. are instructed not to infringe on any rights of the recipient; any such communication violates company policy. If you are not the intended recipient, any disclosure, copying, distribution, or action taken or omitted in reliance on this information is strictly prohibited by M.C. Dean, Inc.; please notify the sender immediately by return e-mail, delete this communication and destroy all copies.
4 months, 3 weeks
Re: AD Trust with multiple replicas
by Anil Rathod
I have below Setup:
AD domain: abc.com
maste IPA: node1.idm.abc.com
Replica: node2.idm.com
Both nodes are Enabled server roles: AD trust agent, AD trust controller, CA server, IPA master
Now,
on client side, while client connected with node1, I am able to resolve the AD Users.
but when I connect the client with node2, then AD user not able to resolve.
* anil
This message, together with any attachments, is intended only for the use of the individual or entity to which it is addressed and may contain confidential and/or privileged information. If you are not the intended recipient(s), or the employee or agent responsible for delivery of this message to the intended recipient(s), you are hereby notified that any dissemination, distribution or copying of this message, or any attachment, is strictly prohibited. If you have received this message in error, please immediately notify the sender and delete the message, together with any attachments, from your computer. Thank you for your cooperation.
4 months, 3 weeks
Re: Create IPA user via LDAP
by Rob Crittenden
Ronald Wimmer wrote:
> On 02.01.24 17:57, Ronald Wimmer via FreeIPA-users wrote:
>> On 02.01.24 16:27, Rob Crittenden wrote:
>>> Ronald Wimmer via FreeIPA-users wrote:
>>>>
>>>>
>>>> On 14.12.23 14:42, Alexander Bokovoy wrote:
>>>>> On Чцв, 14 сне 2023, Ronald Wimmer via FreeIPA-users wrote:
>>>>>> In our company we do have an IAM tool for user management. We need to
>>>>>> create IPA users via this particular tool. I am aware of all IPA
>>>>>> commands or API calls to create/modify or delete a user.
>>>>>>
>>>>>> As the tool does not support FreeIPA yet they asked if there is a way
>>>>>> to manage users by using LDAP only. Could that work? What about
>>>>>> attributes like ipaNTSecurityIdentifier, ipaUniqueID or uidNumber?
>>>>>
>>>>> Learn about lifecycle management. This is your way of integrating with
>>>>> such tools bvy creating staged users:
>>>>> https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/...
>>>>>
>>>>>
>>>>
>>>> I followed the instructions from the documentation.
>>>>
>>>> How could I possibly overcome
>>>>
>>>> Dec 19 09:18:39 tipa01.ipatest.mydomain.at ipa-activate-all[836863]:
>>>> ipa: ERROR: Constraint violation: pre-hashed passwords are not valid
>>>>
>>>> I need to set passwords from the external system.
>>>
>>> You need to enable migration mode (ipa config-mod --enable-migration
>>> true).
>>>
>>> By default a pre-hashed password can only be set once: during the user
>>> add operation.
>>
>> Ok. So this would not work for a password change. So if we need to set
>> an initial password and change that particular password in some point
>> in time the only feasible way is the IPA API, right?
>>
>> Can the immediate password expiration be overridden?
>
> As we have an upcoming please allow me to ask if I got the point here.
>
> I appreciate your support in this matter!
I'd recommend you look into the winsync documentation in IPA. There is a
setting you can configure to allow a pre-hashed password to be written
without marking it as expired (because this is what winsync does).
If you use Kerberos then users are going to have to migrate their
password every time it changes on the external system.
rob
4 months, 3 weeks
Ignore authselect configuration
by Finn Fysj
Hi,
First: is it possible to ignore the authselect configuration during FreeIPA server installation?
Reason I'm asking is because we're hardening the OS before we run FreeIPA installation, meaning there have been issues with UMASK and authselect overwrite.
FreeIPA installation does not support UMASK stricter than 022.
The FreeIPA installation also changes our authselect configuration as we configure this as part of our OS hardening and setting the immutable flag on some of these config files.
We don't want FreeIPA installation to configure the authselect. Unfortunately we haven't found anything in /usr/lib/python3.9/site-packages/ipaplatform/redhat/authconfig.py that let us do this. Is it possible to ignore this?
4 months, 4 weeks
(no subject)
by Finn Fysj
> Finn Fysj via FreeIPA-users wrote:
>
> There is not currently.
>
> I guess I would suggest hardening after installing IPA. You're moving
> into an untested/unsupported configuration so keep that in mind. There
> be dragons.
>
> rob
Thanks Rob.
However, does that mean we can get surprises if we're so bold and configure e.g UMASK after IPA installation etc.?
5 months
krb5kdc: No such file or directory
by Roberto Cornacchia
Hi there, clients are having trouble with kerberos authentication:
$ kinit -V user
Using existing cache: xxxxxxxxxx:yyyyy
Using principal: user(a)SUB.EXAMPLE.COM <roberto(a)SUB.EXAMPLE.COM>
Password for user(a)SUB.EXAMPLE.COM <roberto(a)SUB.EXAMPLE.COM>:
kinit: Generic error (see e-text) while getting initial credentials
On the ipa server, /var/log/krb5kdc.log says:
Dec 24 14:40:34 ipa01.sub.example.com krb5kdc[3324](info): AS_REQ (6 etypes
{aes256-cts-hmac-sha384-192(20), aes128-cts-hmac-sha256-128(19),
aes256-cts-hmac-sha1-96(18), aes128-cts-hmac-sha1-96(17),
camellia256-cts-cmac(26), camellia128-cts-cmac(25)}) <
<http://192.168.0.202/>IP>: NEEDED_PREAUTH: user(a)SUB.EXAMPLE.COM
<roberto(a)SUB.EXAMPLE.COM> for krbtgt/SUB.EXAMPLE.COM(a)SUB.EXAMPLE.COM,
Additional pre-authentication required
Dec 24 14:40:34 ipa01.sub.example.com krb5kdc[3324](info): closing down fd
11
Dec 24 14:40:51 ipa01.sub.example.com krb5kdc[3324](info): AS_REQ :
handle_authdata (2)
Dec 24 14:40:51 ipa01.sub.example.com krb5kdc[3324](info): AS_REQ (6 etypes
{aes256-cts-hmac-sha384-192(20), aes128-cts-hmac-sha256-128(19),
aes256-cts-hmac-sha1-96(18), aes128-cts-hmac-sha1-96(17),
camellia256-cts-cmac(26), camellia128-cts-cmac(25)}) <
<http://192.168.0.202/>IP>: HANDLE_AUTHDATA: user <roberto(a)SUB.EXAMPLE.COM>
@SUB.EXAMPLE.COM <roberto(a)SUB.EXAMPLE.COM> for krbtgt/
SUB.EXAMPLE.COM(a)SUB.EXAMPLE.COM, No such file or directory
Dec 24 14:40:51 ipa01.sub.example.com krb5kdc[3324](info): closing down fd
11
Dec 24 14:40:57 ipa01.sub.example.com krb5kdc[3324](info): AS_REQ (4 etypes
{aes256-cts-hmac-sha1-96(18), aes128-cts-hmac-sha1-96(17),
aes256-cts-hmac-sha384-192(20), aes128-cts-hmac-sha256-128(19)}) <
<http://192.168.0.16/>IP>: NEEDED_PREAUTH: ldap/
ipa01.sub.example.com(a)SUB.EXAMPLE.COM for krbtgt/
SUB.EXAMPLE.COM(a)SUB.EXAMPLE.COM, Additional pre-authentication required
Dec 24 14:40:57 ipa01.sub.example.com krb5kdc[3324](info): closing down fd
11
Dec 24 14:40:57 ipa01.sub.example.com krb5kdc[3324](info): AS_REQ (4 etypes
{aes256-cts-hmac-sha1-96(18), aes128-cts-hmac-sha1-96(17),
aes256-cts-hmac-sha384-192(20), aes128-cts-hmac-sha256-128(19)}) <
<http://192.168.0.16/>IP>: ISSUE: authtime 1703425257, etypes
{rep=aes256-cts-hmac-sha1-96(18), tkt=aes256-cts-hmac-sha1-96(18),
ses=aes256-cts-hmac-sha1-96(18)},
ldap/ipa01.sub.example.com(a)SUB.EXAMPLE.COM for
krbtgt/SUB.EXAMPLE.COM(a)SUB.EXAMPLE.COM
Dec 24 14:40:57 ipa01.sub.example.com krb5kdc[3324](info): closing down fd
11
Dec 24 14:40:57 ipa01.sub.example.com krb5kdc[3324](info): TGS_REQ (4
etypes {aes256-cts-hmac-sha384-192(20), aes128-cts-hmac-sha256-128(19),
aes256-cts-hmac-sha1-96(18), aes128-cts-hmac-sha1-96(17)}) <
<http://192.168.0.16/>IP>: ISSUE: authtime 1703425257, etypes
{rep=aes256-cts-hmac-sha1-96(18), tkt=aes256-cts-hmac-sha1-96(18),
ses=aes256-cts-hmac-sha1-96(18)},
ldap/ipa01.sub.example.com(a)SUB.EXAMPLE.COM for
ldap/ipa02.sub.example.com(a)SUB.EXAMPLE.COM
Dec 24 14:40:57 ipa01.sub.example.com krb5kdc[3324](info): closing down fd
11
There are 2 ipa servers, ipa01 (Rocky 9.3, ipa 4.10.2) and ipa02 (Rock 9.1,
ipa4.10.0), both with CA and DNS. ipa02 is CRL master.
On both, ipa-healthcheck doesn't find any issue.
Also: kinit fails from within ipa01, succeeds from within ipa02.
The issue seems to be in ipa01, and I have already tried to reinstall it
from scratch. One thing that is different is the version.
Could you please help me figure out what's wrong?
Best regards,
Roberto
5 months
