Skip to main content

Setting up Spacewalk to use FreeIPA as authentication source

This post is about setting up Spacewalk to integrate to FreeIPA'sauthentication (ldap/kerberos).
First of all, why should you integrate Spacewalk to FreeIPA? FreeIPA gives you the option to control the access policies using keytabs and you can manage your users centrally. 

So let's get started. I assume you have a functional Spacewalk and FreeIPA-Server set up and the Spacewalk-Server added as client to your domain.

Log in to your FreeIPA-Server and add the http-keytab to your Spacewalk-Server:
 [archy@ipa01 ~]$ ipa service-add HTTP/spacewalk01.archyslife.lan
Next run the script provided by the spacewalk-project / red hat to set up the spacewalk-services
 [archy@spacewalk ~]$ sudo spacewalk-setup-ipa-autchentication
When that's finished, sign in to your IPA-Server again and add the Host Based Access Control Service. I've named it 'spacewalk'
 [archy@ipa01 ~]$ ipa hbacsvcs-add spacewalk
Next add a hbac-rule for allowing defined users to retrieve a keytab and authenticate using ldap / kerberos. I've named the rule spacewalk-management just like the group. 
 [archy@ipa01 ~]$ ipa hbacrule-add spacewalk-management
Next, We'll add the host, service and users which are allowed to login on to the spacewalk-service.
 [archy@ipa01 ~]$ ipa hbacrule-add-user --groups=spacewalk-management spacewalk-management  
 [archy@ipa01 ~]$ ipa hbacrule-add-service --hbacsvcs=spacewalk spacewalk-management  
 [archy@ipa01 ~]$ ipa hbacrule-add-host --hosts=spacewalk01.archyslife.lan spacewalk-management
You can test if the authentication would work by running:
 [archy@ipa01 ~]$ ipa hbactest --user=archy--host=spacewalk01.archyslife.lan --service=spacewalk
Labels:

Comments

  1. AnonymousDecember 12, 2017 at 7:14 PM

    Great article. I am currently trying to connect a Solaris 10 server to a FreeIPA in a lab environment but things are not working out. Any helpful suggestions or links to tutorials will be highly appreciated.

    ReplyDelete
    Replies
    1. Adrian "Archy"January 9, 2018 at 11:01 PM

      Hey there,
      thanks for the kind words. Sorry for the late reply, I haven't tried this yet but I'd start by editing the following files:
      /etc/nsswitch.conf - for password and group lookups
      /etc/pam.conf - configure to use kerberos first
      /etc/ldap.conf - configure to integrate it to FreeIPA's 389DS-Server
      /etc/krb5/krb5.conf - configure to get kerberos-tickets
      This should be all configs on solaris. All there is left, would be creating a principal for the client and generating a keytab which you copy to the solaris-client in theory.
      I'd check out the FreeIPA-Homepage and their IRC-Channel on freenode. So far I have not seen any tutorials for this specific setup.

      Delete
  2. NarayanAugust 26, 2020 at 1:40 PM

    Hi Archy
    I have implemented your steps for spacewalk integration with freeIpa but it's not working.
    I have verified all files and executed all steps but still spacewalk is not authenticating any freeIpa user .
    Can you please help on this.
    Spacewalk GitHub link for free ipa authentication but
    that also did not work

    ReplyDelete
    Replies
    1. Adrian "Archy"August 28, 2020 at 9:27 AM

      Hi Narayan,
      check your logs in spacewalk and the permissions in freeipa using
      'ipa hbac-test'. I cannot reproduce this anymore since I've switched to foreman/katello 2 years ago.

      Delete

Post a Comment

Popular posts from this blog

Dynamic DNS with BIND and ISC-DHCP

I personally prefer to work with hostnames instead of ip-addresses. If you have anything like freeipa or active directory, it will do that for you by registering the client you added to your realm to the managed dns and edit the records dynamically. We can achieve the same goal with just bind and isc-dhcp. I'll use a raspberry pi with raspbian 9 for this setup. So here is a quick tutorial on how to configure the isc-dhcp-server to dynamically update bind. First set a static ip to your server. [archy@ddns ~]$ sudo vim /etc/network/interfaces # interfaces(5) file used by ifup(8) and ifdown(8) # Please note that this file is written to be used with dhcpcd # For static IP, consult /etc/dhcpcd.conf and 'man dhcpcd.conf' # Include files from /etc/network/interfaces.d: source-directory /etc/network/interfaces.d auto eth0 iface eth0 inet static address 172.31.30.5 network 172.31.30.0 broadcast 172.31.30.255 netmask 255.255.255.0
Post a Comment
Read more

LACP-Teaming on CentOS 7 / RHEL 7

What is teaming? Teaming or LACP (802.3ad) is a technique used to bond together multiple interfaces to achieve higher combined bandwith. NOTE: every clients speed can only be as high as the single link speed of one of the members. That means, if the interfaces I use in the bond have 1 Gigabit, every client will only have a maximum speed of 1 Gigabit. The advantage of teaming is, that it can handle multiple connections with 1 Gigabit. How many connections depends on the amount of your network cards. I'm using 2 network cards for this team on my server. That means I can handle 2 Gigabit connections at full rate on my server provided the rest of the hardware can deliver that speed. There also exists 'Bonding' in the Linux world. They both do the same in theory but  for a detailed comparison check out this  article about teaming in RHEL7 . To create a teaming-interface, we will first have to remove all the interface configurations we've done on the (soon to be) sla
8 comments
Read more

Push logs and data into elasticsearch - Part 2 Mikrotik Logs

This is only about the setup of different logging, one being done with Filebeat and the other being done with sending logging to a dedicated port opened in Logstash using the TCP / UDP Inputs. Prerequesites: You'll need a working Elasticsearch Cluster with Logstash and Kibana. Start by getting the Log Data you want to structure parsed correctly. Mikrotik Logs are a bit difficult since they show you Data in the interface which is already enriched with Time / Date. That means a message that the remote logging will send to Logstash will look like this: firewall,info forward: in:lan out:wan, src-mac aa:bb:cc:dd:ee:ff, proto UDP, 172.31.100.154:57061->109.164.113.231:443, len 76 You can check them in the grok debugger and create your own filters and mapping. The following is my example which might not fit your needs. Here are some custom patterns I wrote for my pattern matching: MIKROTIK_DATE \b(?:jan(?:uary)?|feb(?:ruary)?|mar(?:ch)?|apr(?:il)?|may|jun(?:e)?|jul(?
9 comments
Read more

FreeIPA - Integrating your DHCPD dynamic Updates into IPA

I recently went over my network configuration and noticed that the dhcp-leases were not pushed into the IPA-DNS yet. So I thought, why not do it now. The setup is very similar to setting it up on a single bind instance not managed by IPA (I've already written a guide about this here ). recently went over my network configuration and I noticed that I've never put my My setup is done with the following hosts: ipa01.archyslife.lan - 172.31.0.1 inf01.archyslife.lan - 172.31.0.5 First of all, create a rndc-key: [archy@ipa01 ~]$ sudo rndc-confgen -a -b 512 This will create the following file '/etc/rndc-key' [archy@ipa01 ~]$ sudo cat /etc/rndc.key key "rndc-key" { algorithm hmac-md5; secret "secret_key_here=="; }; We also need to make named aware of the rndc-key and allow our remote dhcp server to write dns entries: [archy@ipa01 ~]$ sudo vim /etc/named.conf ... include "/etc/rndc-key&quo
2 comments
Read more

SSSD - Debugging PAM permission denied

Sometimes there's weird errors in IT that occur on random chance. I've had such an encounter with SSSD in combination with IPA(+AD-Trust) recently, where only sometimes, a connection to one of the IPA-Servers would fail with this error: Jul 13 13:36:42 ipa02.archyslife.lan sshd[3478]: pam_sss(sshd:account): Access denied for user runner: 4 (System error) Jul 13 13:36:42 ipa02.archyslife.lan sshd[3478]: fatal: Access denied for user runner by PAM account configuration [preauth] In my case, it was only happening sometimes when running a basic system setup role using ansible on every host in the entire environment. This way, there was no consistent pattern besides being the same host every time if it failed. First up, add the 'debug_level=X' to every section required in the /etc/sssd/sssd.conf where X is a number from 1 to 10 with 10 being the most verbose. Afterward, restart sssd and check the logs for any obvious problems. 1) If you are using local users, check the
Post a Comment
Read more