| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
| |
Try as hard as possible to store as much data as we can.
|
| |
|
|
|
|
| |
- making the realm part upper case is now optional and done in the
LDAP backend
- using a username@realm UPN is now optional
|
| |
|
|
|
| |
If available the original DN and the user principle will be stored
in sysdb.
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
Retrieving ldap results and storing users could sometimes results in race
conditions where the final ldap result was retrieved before the store operations
where finished resulting in the operations to be aborted before termination.
Implement a serialization mechanism per operation.
|
| | |
|
| |
|
|
|
|
|
|
| |
The sdap_handle might be freed when processing a message.
Rearrange data flow so that the sdap_handle is never used after
a message is processed but a new event (dependent on the handle) is
instead scheduled. If the sdap_handle is freed, the scheduled event
is also removed and not fired
|
| | |
|
| |
|
|
|
|
|
| |
The way openldap libraries work, require to have a single engine per
connection as all replies are read at the same time. So we need to
always read anything that comes in from the wire and then loop to
dispatch results to the requests that are waiting.
|
| |
|
|
| |
This uses and exapands the async helpers.
|
| | |
|
|
|
These functions use the tevent_req async model, where a pair
of _send/_recv functions pilot requests, with additional helpers
like _done functions, and where needed multiple stage helpers.
|
