sssd.spec for SLES
by Sergei V. Kovylov
Here you may find a patch for sssd.spec file which provide correct
build sssd for SLES (testes on SLES10SP1).
In brief:
There are 3 essences:
redhat
fedora
sles
which are detected by /etc/<vendor release file> existence (ex.
/etc/SuSE-release) in spec and all necessary actions are doing along
the OS detection.
Additionally for SLES there is "--without-selinux" flag while
configuring, as SLES doesn't support SELinux.
14 years, 1 month
[PATCHES] Collection, Ref Array, ELAPI
by Dmitri Pal
Hi,
This is resubmission of the two earlier withdrawn patches (Ref Array and
ELAPI) and addition of a new patch to collection.
For details see the patch comments.
Note about ELAPI patch: it is huge so it is zipped. This patch includes
the first cut of eliminating the elapi_test directory altogether. The
directory is not built any more so there is no need to spend much time
looking at the files that were updated in this directory. They will be
either removed in follow up patches or moved to elapi directory.
--
Thank you,
Dmitri Pal
Engineering Manager IPA project,
Red Hat Inc.
-------------------------------
Looking to carve out IT costs?
www.redhat.com/carveoutcosts/
14 years, 2 months
[PATCH] fix for #323
by Simo Sorce
Now the upgrade process can cope with converting ols ssd.ldb files into
multiple databases even if the new config file does not include a
"local" provider anymore.
Tested with a v1 db file and seem to work fine with and w/o a LOCAL
provider defined in the configuration.
Simo.
--
Simo Sorce * Red Hat, Inc * New York
14 years, 2 months
Two more logo drafts
by Johannes von Bargen
Hi,
I created two more logo drafts...
Please check them out and let me know what you think!
--
Johannes von Bargen
14 years, 2 months
sssd 1.0 potential issue?
by Jeff Schroeder
I've not been able to reproduce this just yet, but when installing
sssd 1.0 via puppet, it didn't seem to come up right. It only started
the LDAP provider and nothing else. It seems like this should be
critical and the watchdog parent should spawn the other child
providers such as the pam and nss providers.
root(a)core022.lax02 ~ # ps -efH | grep sss[d]
root 5347 1 0 10:20 ? 00:00:00 /usr/sbin/sssd -f -D
root 5348 5347 0 10:20 ? 00:00:00
/usr/libexec/sssd/sssd_be -d 0 --debug-to-files --domain LDAP
[sssd]
config_file_version = 2
domains = LDAP
reconnection_retries = 3
sbus_timeout = 30
services = nss, pam
[nss]
filter_groups = root,core
filter_users = root,core
reconnection_retries = 3
[pam]
reconnection_retries = 3
[domain/LDAP]
auth_provider = ldap
cache_credentials = TRUE
chpass_provider = ldap
enumerate = TRUE
id_provider = ldap
ldap_group_search_base = ou=Groups,o=int
# Ignore ldap pwd policies so password changes work with shadow*
attributes in ldap
ldap_pwd_policy = none
ldap_tls_reqcert = never
ldap_uri = ldap://server1.site1/ ldap://server2.site2 ldap://server3.site3
ldap_user_search_base = o=int
min_id = 1
timeout = 60
Needless to say, this makes it a bit difficult to login. Any pointers
to if the config is wrong in this instance? In any case, it seems like
the watchdog was wrong in not starting the other providers. What do
you guys think? Puppet doesn't call anything crazy other than service
sssd {start,restart,reload} in this instance.
--
Jeff Schroeder
Don't drink and derive, alcohol and analysis don't mix.
http://www.digitalprognosis.com
14 years, 2 months
Two more logo drafts
by Johannes von Bargen
Hi,
I created two more logo drafts...
Please check them out and let me know what you think!
--
Johannes von Bargen
14 years, 2 months