Age | Commit message (Collapse) | Author | Files | Lines |
|
The old idmap code created a new mapping if asking the backends failed.
Now with the new layering, if passdb (which is used for our own domain
and builtin), then we need to continue and ask the backends, giving
tdb or whatever the default backend is a chance to create a mapping.
|
|
|
|
|
|
|
|
|
|
init_db
|
|
|
|
idmap_tdb2_db_init
|
|
backends
|
|
|
|
idmap_ad_context
The filter range from the idmap_domain is used now.
|
|
|
|
|
|
Probably got copied from a different location.
|
|
|
|
Now, the idmap_domain range that is centrally parsed is used.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
High level function to create a new mapping for an unmapped sid.
This builds logic that used to reside in the top level idmap code
in the backend.
|
|
Currently this only works with the default domain, calling out
to idmap_ldap_allocate_id(). In the future this will be extended
to also work for non-default domains.
|
|
|
|
this hides this beneath the idmap structure and removes a global variable
|
|
The alloc subsystem is now subordinate to the idmap system.
|
|
|
|
Second step in removing the idmap range from the idmap_ldap_alloc_context.
|
|
First step in removing idmap ranges from the idmap_ldap_alloc_context.
The range from the domain is to be used now.
|
|
|
|
idmap_domain
|
|
|
|
|
|
|
|
|
|
|
|
|
|
High level function to create a new mapping for an unmapped sid.
This builds logic that used to reside in the top level idmap code
in the backend. To be called inside a transaction to guarantee
atomicity of the operation.
|
|
|
|
|
|
|
|
|
|
|
|
instead of alloc_db
|
|
|
|
|