sssd - System Security Services Daemon

Age	Commit message (Collapse)	Author	Files	Lines
2009-11-18	Make the sysdb user and group names case-sensitive	Stephen Gallagher	1	-1/+0

2009-10-09	Remove magicPrivateGroups option	Simo Sorce	1	-0/+1
	In sssd only local is a native mpg domain, and it is forced. All other providers will have to unroll mpg users into a user/group pair of entries in the db. This allows the provider to automatically establish if the remote server provides mpg users w/o possibily conflicting manual configurations on the client trying to force an mpg behavior where none is provided.
2009-09-08	Split database in multiple files	Simo Sorce	1	-14/+14
	The special persistent local database retains the original name. All other backends now have their own cache-NAME.ldb file.
2009-08-27	Upgrade database to 0.2	Simo Sorce	1	-3/+3
	Provides also an upgrade function.
2009-07-03	Rework transaction code to use tevent_req	Simo Sorce	1	-2/+23
	This is part of a set of patches to rewrite sysdb to a hopefully better API, that will also let use use tevent_req async style calls to manipulate our cache.
2009-07-03	Rename sysdb_req to sysdb_handle.	Simo Sorce	1	-3/+3
	This sysdb_req has always really been a transaction handle and not a request. This is part of a set of patches to rewrite transaction support in sysdb to a hopefully better API, that will also let use use tevent_req async style to manipulate our cache.
2009-03-05	Remove _PW_ and _GR_ from SYSDB_ defines	Simo Sorce	1	-2/+1
	Also unify SYSDB_PW_NAME and SYSDB_GR_NAME in SYSDB_NAME and make it "name"
2009-03-04	Improve sysdb	Simo Sorce	1	-2/+0
	Add comments in header files to better explain interfaces and intended usage. Expose function to convert from ldb errors to errnos. Add sysdb_attrs helper to add a long integer as a value.
2009-02-28	Convert sync calls in sysdb to async, transaction dependent, calls.	Simo Sorce	1	-11/+1

2009-02-26	Serialize access to sysdb and also exposes ldb transactions.	Simo Sorce	1	-0/+95
	This is necessary because in ldb only 1 transaction per context is possible and all operations (or new transactions) are nested within it. Will revisit this later when ldb will addresses the problem.