summaryrefslogtreecommitdiffstats
path: root/server/providers/data_provider_be.c
Commit message (Collapse)AuthorAgeFilesLines
* Rebase the code to use talloc, tdb, tevent, ldb as externalSimo Sorce2009-02-261-5/+6
| | | | | | dependencies based on the latest samba code. Convert all references to the old events library to use the renamed tevent library.
* Add PAM responderSumit Bose2009-02-241-1/+137
| | | | | | | Also move responders under server/responder with shared code in server/responder/common Signed-off-by: Simo Sorce <ssorce@redhat.com>
* Proper fix for memory handling problem.Simo Sorce2009-02-241-36/+46
| | | | | | | | | | sbus_message_handler is not responsible anymore for sending back data in any case. Transfer this responsibility to the handler function called. This way both synchronous and asynchronous funstions use the interface the same way and can properly free memory referenced by the reply after the send buffer has been filled in and all copies are done in sbus_conn_send_reply()
* Revert "Fixing serious memory allocation bug in sbus_message_handler."Simo Sorce2009-02-241-30/+41
| | | | | | | | | | | | | | | This reverts commit 13421cbe0af4343f9d110600755ffa756690b282. Conflicts: server/infopipe/infopipe.c server/infopipe/infopipe.h While this solution fixed the contingent memory problem it introduced other problems in handling asynchronous replies. Reverting in preparation for a different way to solve it. Conflicts have been taken care of.
* Fixing serious memory allocation bug in sbus_message_handler.Stephen Gallagher2009-02-231-41/+30
| | | | | | | | | | | | dbus_message_append_args() adds a reference to memory that is not copied to the outgoing message until dbus_connection_send() is called. Since we compile our reply messages in functions and then return the reply, we need a mechanism for deleting allocated memory after invoking dbus_connection_send. I have changed the arguments to sbus_msg_handler_fn so that it takes a talloc ctx containing the sbus_message_handler_ctx and a pointer to a reply object. We can now allocate memory as a child of the reply context and free it after calling dbus_connection_send.
* Make backend requests asyncSimo Sorce2009-02-131-14/+223
|
* Always pass teh database path explicitly, so that test cases can useSimo Sorce2009-02-131-1/+1
| | | | | throw away databases Check version and init main db if empty
* Remove dp_cli_sbus_initSimo Sorce2009-02-121-12/+5
|
* Refactoring the monitor code and SBUS utility functions.Stephen Gallagher2009-01-271-11/+59
|
* Add code to make it easier to reconnect in case the serverSimo Sorce2009-01-141-15/+3
| | | | | is not available immediately or drops the dbus connection. First step is the nss connection to the data provider.
* Regroup database rleated functions under db andSimo Sorce2009-01-121-3/+2
| | | | rename everything with the sysdb suffix.
* Turn ldap_provider.c into proxy.c and make it possible to load just anySimo Sorce2009-01-111-1/+2
| | | | libnss library through config directives on the domain object
* The code now successfully sends a getpwnam request to a remote LDAP server,Simo Sorce2009-01-081-18/+53
| | | | | | and caches the result in LDAP. Still chasing a bug that does not let NSS known that the BE was successful. This makes NSS timeout the client and not return any results yet.
* Add more infrastructure to data provider to dispatch requests (still untested).Simo Sorce2009-01-061-153/+87
| | | | | Add helper functions to connect to the data provider. Add some plumbing to the ldap provider (still untested).
* Fix dp client to connect to the right dbus pipeSimo Sorce2009-01-051-11/+16
|
* Adding a parameter to the sbus_service_sbus_init function to allow passing ↵Stephen Gallagher2008-12-151-1/+1
| | | | in an sbus_conn_destructor_fn to the sbus_new_connection() function. Fixing minor warning about the usage of talloc_reference.
* Initial work on a test provider using the gross hack of dlopen()ing nss_ldapSimo Sorce2008-12-101-8/+9
| | | | :-)
* Change data provider into a hub, where backends (ldap, nis, ipa providers)Simo Sorce2008-12-081-0/+515
and frontends (pam, nss, ... modules) can connect to.