On Wed, Jul 24, 2013 at 07:11:28PM -0400, Dmitri Pal wrote:
> On 07/24/2013 03:41 PM, Licause, Al (CSC AMS BCS - UNIX/Linux Network
> Support) wrote:
> > Thanks Jakob,
> >
> > I suspect I'll have at least one unhappy customer if they can't upgrade.
> >
> > Should we not be able to use sudo with sss
On 07/24/2013 03:41 PM, Licause, Al (CSC AMS BCS - UNIX/Linux Network
Support) wrote:
> Thanks Jakob,
>
> I suspect I'll have at least one unhappy customer if they can't upgrade.
>
> Should we not be able to use sudo with sssd, is it possible to use straight
> ldap.conf
> and shutdown/bypass sssd
Stephen,
Ah. I did not realize that. I thought some directory information might be
coming over in plaintext as with normal LDAP binds. Since this is not the
case, I'm happy!
Thanks!
-Chris
On Wed, Jul 24, 2013 at 4:39 PM, Stephen Gallagher wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: S
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/24/2013 03:50 PM, Chris Hartman wrote:
> Hi guys!
>
> Is there anyway I can force my SSSD clients running 1.9.5 (Ubuntu
> 12.04) and 1.9.2 (CentOS 6) to bind to LDAPs (port 636) instead of
> LDAP (port 389) when my providers are all set to "ad"?
Hi guys!
Is there anyway I can force my SSSD clients running 1.9.5 (Ubuntu 12.04)
and 1.9.2 (CentOS 6) to bind to LDAPs (port 636) instead of LDAP (port 389)
when my providers are all set to "ad"?
Consequently, I'll need to specify a certificate to be used to verify the
server's authenticity.
I'
Thanks Jakob,
I suspect I'll have at least one unhappy customer if they can't upgrade.
Should we not be able to use sudo with sssd, is it possible to use straight
ldap.conf
and shutdown/bypass sssd in V6.3 of RHEL for example ?
I'm trying to get it to work and having a difficult time.
Al
Al
On Wed, Jul 24, 2013 at 06:41:38PM +, Licause, Al (CSC AMS BCS - UNIX/Linux
Network Support) wrote:
> Ok...that did it.
>
> I installed libsss_sudo-1.9.2-82.el6.x86_64.rpm on two different RHEL V6.4
> systems and now sudo
> is working through sssd and our ldap server.
>
> But I am not findi
Ok...that did it.
I installed libsss_sudo-1.9.2-82.el6.x86_64.rpm on two different RHEL V6.4
systems and now sudo
is working through sssd and our ldap server.
But I am not finding this library in the RHEL V6.3 distro, so does that mean
sudo with sssd can not
be used in Red Hat prior to V6.4 ?
Guess I should look before asking.
I found the following rpm that was not installed on my systems:
libsss_sudo-1.9.2-82.el6.x86_64.rpm
I guess I'll try to install that and give it shot.
Al Licause
From: Licause, Al (CSC AMS BCS - UNIX/Linux Network Support)
Sent: Wednesday, July 24, 2013 11:03 A
I guess I should have mentioned that I have the following installed:
sudo-1.8.6p3-7.el6.x86_64
Al Licause
From: Licause, Al (CSC AMS BCS - UNIX/Linux Network Support)
Sent: Wednesday, July 24, 2013 10:57 AM
To: 'End-user discussions about the System Security Services Daemon'
Subject: Not finding
I thought I had this working only to realize on the two systems it appeared to
be working, I was actually
using the local sudoers file.
Now that I have that and a few other nits covered, I think I almost have this
working but when the ldap user
attempts to sudo, they get the following:
$ sudo d
=== SSSD 1.11 beta 2 ===
The SSSD team is proud to announce the second beta release of version 1.11
of the System Security Services Daemon.
This pre-release does not bring substantial changes visible to the end-user. It
is intended to be part of the development of FreeIPA 3.
12 matches
Mail list logo
