Skip to main content

LDAP testing

[root@server9 opt]# vi /etc/sssd/sssd.conf
Add the following at the bottom (may affect performance)
Enumerate = True

# getent passwd
This will poll the server for a refresh, you can then

[root@server9 opt]# getent passwd
... LDAP USERS WILL BE DISPLAYED ...

[root@server9 opt]# yum list | grep openldap
This system is not registered with RHN.
RHN support will be disabled.
openldap.x86_64 2.4.19-15.el6 @anaconda-RedHatEnterpriseLinux-201009221801.x86_64/6.0
compat-openldap.i686 2.4.19_2.3.43-15.el6 base
compat-openldap.x86_64 2.4.19_2.3.43-15.el6 base
openldap.i686 2.4.19-15.el6 base
openldap-clients.x86_64 2.4.19-15.el6 base
openldap-devel.i686 2.4.19-15.el6 base
openldap-devel.x86_64 2.4.19-15.el6 base
openldap-servers.x86_64 2.4.19-15.el6 base
openldap-servers-sql.x86_64 2.4.19-15.el6 optional

[root@server9 opt]# yum install openldap-clients

[root@server9 opt]# ldapsearch -x -ZZ

Comments

Post a Comment

Popular posts from this blog

PXE boot a LiveCD image

Summary: I have wanted to build a kickstart environment which hosted a "rescue CD" or LiveCD to allow you to boot over the network after you blew your stuff up and needed to repair a few things.  Today I have worked through a method of doing so, with the help of the people who published a succinct script with the Red Hat Enterprise Virtualization Hypervisor.  (the script will be at the bottom of this post - if I have somehow not followed the GPL, please let me know and I will correct whatever is necessary) NOTE/Warning: The boot will fail due the initrd being too large (645mb).  I'm not sure how to proceed.  This procedure worked for RHEVh, because it is quite a bit smaller.  Hopefully I can report back with progress on this? :-$ Procedure: download your LiveCD image to /export/isos/RESCUE/Fedora-16-i686-Live-Desktop.iso # cd /var/tmp # vi livecd-iso-to-pxeboot (populate the file with the script shown below) # chmod 754 ./livecd-iso-to-pxeb...
2 comments
Read more

"Error getting authority: Error initializing authority: Could not connect: No such file or directory (g-io-error-quark, 1)"

"Error getting authority: Error initializing authority: Could not connect: No such file or directory (g-io-error-quark, 1)" One issue that may cause this to arise is if you managed to break your /etc/fstab We had an engineer add a line with the intended options of "nfsvers=3" but instead added "-onfsvers=3" and it broke the system fairly catastrophically.
Post a Comment
Read more

P2V using dd for KVM-QEMU guest

Preface: I have certainly not exhaustively tested this process.  I had a specific need and found a specific solution that worked. Situation:  I was issued a shiny new laptop running Red Hat Enterprise Linux 7 (with Corp VPN, certs, Authentication configuration, etc...)  The image was great, but I needed more flexibility on my bare metal.  So, my goal was to P2V the corporate image so I could just run it as a VM. * Remove corporate drive and install new SSD * install corp drive in external USB-3 case * Install RHEL 7 on new SSD * dd old drive to a disk-image file in a temp location which will be an image which is the same size as your actual drive (unless you have enough space in your destination to contain a temp and converted image) * convert the raw disk-image to a qcow file while pushing it to the final location - this step should reduce the disk size - however, I believe it will only reduce/collapse zero-byte blocks (not just free space - i.e. if you de...
1 comment
Read more