summaryrefslogtreecommitdiffstats
path: root/source3/include/tldap.h
Commit message (Collapse)AuthorAgeFilesLines
* If the connection is down, don't try another write.Volker Lendecke2009-06-281-0/+1
|
* Add tldap paged searches, together with two helper routinesVolker Lendecke2009-06-201-0/+2
|
* Reorganize retrieving errors and server-sent controlsVolker Lendecke2009-06-201-9/+5
| | | | | | | This attaches the data to the tldap_message instead of the tevent_req. It adds tldap_ctx_lastmsg() to retrieve the last message for the users of the sync wrappers.
* tldap control supportVolker Lendecke2009-06-201-2/+6
|
* Prepare control supportVolker Lendecke2009-06-201-19/+33
| | | | | | | | | We will have arrays of controls passed to tldap.c. Follow a mantra from the classic book "Thinking Forth" by Leo Brodie: Favor counts over terminators :-) This makes the parameter lists to tldap pretty long, but everyone will have wrapper routines anyway, see for example tldap_search_fmt. And the OpenLDAP manpages call the non-_ext routines deprecated, probably for a reason.
* Make tevent_req_is_ldap_error publicVolker Lendecke2009-06-191-0/+2
|
* Add tldap_context_[gs]etattrVolker Lendecke2009-06-191-0/+3
| | | | | | | | | | This adds the ability to attach extended information to a tldap_context. This will become useful once we start to do automatic reconnects for example, a callback function might want attach a pointer to credentials so that it can rebind. The initial user of this will be a cached rootdse, so that things like the ability to do paged searches can be cached.
* Add debugging facility to tldap, analogous to teventVolker Lendecke2009-06-121-0/+15
|
* req_del and req_abandon are ASN1_APPLICATION_SIMPLEVolker Lendecke2009-06-071-2/+4
| | | | Ok, ASN1_APPLICATION everywhere was too easy :-)
* Fix after making tldap independent of ldap.hVolker Lendecke2009-06-071-21/+24
|
* Attempt to fix the build without system-ldap.Volker Lendecke2009-06-061-1/+1
| | | | I really tried, but I knew I would miss something... :-)
* Add the early start of an async ldap libraryVolker Lendecke2009-06-061-0/+237
There's a lot of things this does not do yet: For example it does not parse the reply blob in the sasl bind, it does not do anything with controls yet, a lot of the ldap requests are not covered yet. But it provides a basis for me to play with a pdb_ads passdb module.