similar to: Trust between Samba AD and FreeIPA Domain

Hi, I wonder if someone here is already authing against FreeIpa with some latest Ubuntu/SSSD install. I'm on on Ubuntu 15.10 for samba to test this out: Samba: 4.1.17 SSSD: 2.1.17 Freeipa: 4 on CentOS 7 I don't need an AD so I'm folling this what still does not apply. http://www.freeipa.org/page/Howto/Integrating_a_Samba_File_Server_With_IPA I hope someone can help out and

doing some googling, this seems to be about the most current/relevant thing I have found wrt to running freeipa server on CentOS http://howtoforge.com/how-to-build-rhel-ipa-rpms-for-centos-5 which I'm not totally adverse to doing but I have to ask, is there something packaged? (I've looked in 'testing' and in 'extras' and in epel) Has anyone followed some other

This lays 90% of the groundwork needed on the server side to support the use of a remote ipa server. Leaving the option disabled in the installer until the necessary node integration(dns/keytab placementi location) is completed Also apply: [PATCH server] update ovirt-add-host to use ipa commands instead of kadmin.local [PATCH server] separate ipa common tasks freeipa::common and rename

Hello everybody, What is the status of the freeipa/sssd and samba conflicts in the repositories? I can not wrap my mind around that two big packages are not getting security updates anymore, because they are conflicting. I will go to FOSDEM in Belgium this year to figure out more, but I am considering moving my centos systems to rockylinux. Kind regards, Jelle de Jong On 12/16/22 16:59,

On 13/08/2019 13:33, Jonathan Billings wrote: > On Tue, Aug 13, 2019 at 01:02:58PM +0100, lejeczek via CentOS wrote: > >> I wonder if anybody might version of freeIPA in RHEL? >> >> I hear it's 4.6.6 and if that's true then when will Centos get it I >> might ask. > RHEL 7.7 has FreeIPA 4.6.5, and eventually CentOS will get that > version, but it's

Hello all, Is anybody using http://freeipa.org on a CentOS 6 server? Is it working well? Thanks. Boris.

This patch series adds a new virt-sysprep operation to offline unenroll a guest from FreeIPA. It does so by removing some configuration files and certificates. It requires a change in libguestfs-common before the series is applied. Pino Toscano (4): customize: port do_run to run_in_guest_command sysprep: add a update_system_ca_store side effect sysprep: ca-certificates: request system CA

hi guys I wonder if anybody might version of freeIPA in RHEL? I hear it's 4.6.6 and if that's true then when will Centos get it I might ask. many thanks, L.

sorry guys to spam a bit - I hope someone from redhat could check whether - freeipa-users at redhat.com - is up & ok? I've been a subscriber for a couple of years but now, suddenly(?) I cannot mail there, I get: " Sorry, we were unable to deliver your message to the following address. <freeipa-users at redhat.com>: 554: 5.7.1 <freeipa-users at redhat.com>: Recipient

Hi, We're looking to run freeipa 4.1.1 on CentOS 7. 1. after include: * mkosek-freeipa-epel-7.repo 2. Write this: * yum install freeipa-server 3. I get this error: * Error: Package: pki-base-10.2.0-3.el7.centos.noarch (mkosek-freeipa) * Requires: jackson-jaxrs-json-provider I would appreciate any ideas. -- Cosme Faria Corr?a

does anybody see this: unning transaction Warning: RPMDB altered outside of yum. ** Found 8 pre-existing rpmdb problem(s), 'yum check' output follows: ipa-admintools-4.4.0-14.el7.centos.noarch has installed conflicts freeipa-admintools: ipa-admintools-4.4.0-14.el7.centos.noarch ipa-client-4.4.0-14.el7.centos.x86_64 has installed conflicts freeipa-client:

When I set up a machine with CentOS 8, I used the "Enterprise Login" in the initial setup wizard to authenticate against my FreeIPA server. This worked fine, and I have no issues logging in with that initial user. However, I am unable to use GDM or the console to login as any *other* valid user from FreeIPA. From GDM I get something like "Sorry, that didn't work" and

Hi Natxo, On Fri, 2012-11-30 at 13:06 +0100, Natxo Asenjo wrote: > hi, > > I'm following the howto on > http://freeipa.org/page/Libvirt_with_VNC_Consoles to authenticate > users voor virsh with ipa. > > I have it mostly working :-) except for the fact that libvirtd is not > respecting the sasl_allowed_username_list parameter. > > If I do not set it, and I have

On Tue, Dec 13, 2016 at 04:44:06PM +0000, lejeczek wrote: > does anybody see this: > > unning transaction > Warning: RPMDB altered outside of yum. > ** Found 8 pre-existing rpmdb problem(s), 'yum check' output > follows: > ipa-admintools-4.4.0-14.el7.centos.noarch has installed conflicts > freeipa-admintools: ipa-admintools-4.4.0-14.el7.centos.noarch >

Hello I just finished setting up FreeIPA with Dovecot + Postfix + Saslauthd. I can easily access to mails using imap via dovecot with gssapi authentication and postfix also delivering mails very well. But I cannot send email from postfix using gssapi authentication (plain and login authentication working fine) because saslauthd is not specifying realm when requesting service from freeipa domain.

Hi, I''m faced with the question if we should be doing user management directly using freeipa (an integrated LDAP, Kerberos, CA, etc) or by manipulating freeipa using Puppet. Installation and configuration of the service is already performed through Puppet so this only concerns the data stored by freeipa (users, groups, sshkeys, sudo permissions, etc). Pros of puppet: - everything

The dovecot instance set up with auth_realms and auth_default_realm variables and it is working well. In saslauthd configurations setting same variables giving configuration parsing error (I think it is not right way to configure kerberos realm in saslauthd). However testsaslauthd working without any problems even if I don't specify realm parameter from command line. On 03/10/17 06:17,

Hi, Here's the warning that Yum currently displays: ** Found 3 pre-existing rpmdb problem(s), 'yum check' output follows: ipa-client-4.4.0-14.el7.centos.7.x86_64 has installed conflicts freeipa-client: ipa-client-4.4.0-14.el7.centos.7.x86_64 ipa-client-common-4.4.0-14.el7.centos.7.noarch has installed conflicts freeipa-client-common: ipa-client-common-4.4.0-14.el7.centos.7.noarch

Hi everyone, I am new to this mailing list. At the moment I would like to migrate all of my users from Microsoft Active Directory to Open Source, and what I have in mind is getting it into Samba 4. In extending the functionality of it, I decided to intergrate FreeIPA as the backend to Samba 4. I saw some obsolete reference on how to use FreeIPA as Samba 4 backend, but I don't know where

Hello, I'm figuring out how to auth users against FreeIPA and I wonder if someone did this without GSAPI. My users are stored in a mysql DB where I wonder what I shall use as authname, the username or the mailaddress. As the mailaddress is always unique it could be best but if a user has multiple mailaddresses under seperate domains username might be better. Any clue here and maybe an