summaryrefslogtreecommitdiff
path: root/source4/dsdb
AgeCommit message (Collapse)AuthorFilesLines
2010-07-08s4:acl LDB module - password attributes - check also the "dBCSPwd" attributeMatthias Dieter Wallnöfer1-2/+2
It's also a possible password change/set attribute candidate.
2010-07-08s4:acl LDB module - move a "mem_ctx" creation to the place where it is ↵Matthias Dieter Wallnöfer1-1/+2
actually checked Memory allocations and their result checks should be as tight as possible.
2010-07-08Added a test to prove by default users can change each other's pass if the ↵Nadezhda Ivanova1-0/+25
old is known
2010-07-08s4-dsdb/util: Reorder DSDB_FLAG_* checksKamen Mazdrashki1-30/+30
On good thing about having more clear function interfaces (and forcing callers to specify clearly what they want) is that now I can execute following search: git grep DSDB_FLAG_NEXT_MODULE | wc -l This showed that DSDB_FLAG_NEXT_MODULE flag is about 6 times more frequently used than DSDB_FLAG_OWN_MODULE. So this should reduce branch prediction by six times in this part of the code, right :)
2010-07-08s4-dsdb: Implement module switching in dsdb_module_search_dn()Kamen Mazdrashki1-1/+10
This allows caller to choose from where to start DN search
2010-07-08s4-source4/dsdb/samdb/ldb_modules/acl.c Use DSDB_FLAG_NEXT_MODULE flagKamen Mazdrashki1-5/+12
2010-07-08s4-source4/dsdb/samdb/ldb_modules/linked_attributes.c Use ↵Kamen Mazdrashki1-1/+4
DSDB_FLAG_NEXT_MODULE flag
2010-07-08s4-source4/dsdb/samdb/ldb_modules/naming_fsmo.c Use DSDB_FLAG_NEXT_MODULE flagKamen Mazdrashki1-1/+2
2010-07-08s4-source4/dsdb/samdb/ldb_modules/operational.c Use DSDB_FLAG_NEXT_MODULE flagKamen Mazdrashki1-3/+7
2010-07-08s4-source4/dsdb/samdb/ldb_modules/partition_init.c Use DSDB_FLAG_NEXT_MODULE ↵Kamen Mazdrashki1-3/+6
flag
2010-07-08s4-source4/dsdb/samdb/ldb_modules/pdc_fsmo.c Use DSDB_FLAG_NEXT_MODULE flagKamen Mazdrashki1-1/+2
2010-07-08s4-source4/dsdb/samdb/ldb_modules/repl_meta_data.c Use DSDB_FLAG_NEXT_MODULE ↵Kamen Mazdrashki1-3/+7
flag
2010-07-08s4-source4/dsdb/samdb/ldb_modules/ridalloc.c Use DSDB_FLAG_NEXT_MODULE flagKamen Mazdrashki1-3/+6
2010-07-08s4-source4/dsdb/samdb/ldb_modules/samba_dsdb.c Use DSDB_FLAG_NEXT_MODULE flagKamen Mazdrashki1-2/+4
2010-07-08s4-source4/dsdb/samdb/ldb_modules/schema_load.c Use DSDB_FLAG_NEXT_MODULE flagKamen Mazdrashki1-1/+2
2010-07-08s4-source4/dsdb/samdb/ldb_modules/util.c Use DSDB_FLAG_NEXT_MODULE flagKamen Mazdrashki1-2/+4
2010-07-07s4-dsdb: use ldb_operr() in the dsdb codeAndrew Tridgell43-625/+455
this replaces "return LDB_ERR_OPERATIONS_ERROR" with "return ldb_operr(ldb)" in places in the dsdb code where we don't already explicitly set an error string. This should make is much easier to track down dsdb module bugs that result in an operations error.
2010-07-06s4:new_partition LDB module - fix an uninitalised variable warningMatthias Dieter Wallnöfer1-2/+1
> [ 651/1946] Compiling dsdb/samdb/ldb_modules/new_partition.c > ../dsdb/samdb/ldb_modules/new_partition.c: In function 'new_partition_add': > ../dsdb/samdb/ldb_modules/new_partition.c:195: warning: 'down_req' may be used uninitialized in this function The "down_req" variable isn't used anymore.
2010-07-06s4:dsdb - samdb_result_force_password_change - also when "pwdLastSet" is ↵Matthias Dieter Wallnöfer1-3/+9
"-1" we shouldn't force a password change This value is set by the ADUC console.
2010-07-05s4:dsdb/password_hash: implement DSDB_CONTROL_BYPASS_PASSWORD_HASH_OIDStefan Metzmacher1-0/+20
metze
2010-07-05s4:dsdb: allocate DSDB_CONTROL_BYPASS_PASSWORD_HASH_OIDStefan Metzmacher1-0/+5
When importing users from Samba3 we need to control all values. metze
2010-07-05s4:dsdb/password_hash: fix some c++ compiler warningsStefan Metzmacher1-9/+12
metze
2010-07-05Changed passwords.py to use the correct account as acl checks now pass.Nadezhda Ivanova1-14/+6
2010-07-05s4-dsdb: Implementation of User-Change-Password and User-Force-Password-ChangeNadezhda Ivanova2-85/+226
These CARs need to be checked on password change and password reset operations. Apparently the password attributes are not influenced by Write Property. Single detele operations and modifications of dBCSPwd are let through to the password_hash module. This is determined experimentally.
2010-07-04s4:subtree_rename LDB module - Cosmetic fixesMatthias Dieter Wallnöfer1-3/+4
2010-07-04s4:subtree_delete LDB module - fix comments and add my copyrightMatthias Dieter Wallnöfer1-2/+3
(I've introduced the subtree delete mechanism)
2010-07-03s4:dsdb/tests/python/ldap_schema.py - remove a now useless "schemaUpdateNow" ↵Matthias Dieter Wallnöfer1-10/+0
request "schemaUpdateNow" on s4 is now a non-op and therefore not strictly needed anymore.
2010-07-03s4:urgent_replication.py test - remove unneeded "relax" control parametersMatthias Dieter Wallnöfer1-2/+2
2010-07-03s4:schema_load LDB module - fix a segfault condition on schema refreshMatthias Dieter Wallnöfer1-0/+5
The schema refresh operation itself starts requests from the top of the LDB modules stack (see call "dsdb_schema_set_attributes" - search operations). This doesn't work well when these do perform "dsdb_get_schema" calls. Since the new schema isn't marked as "refreshed" atm (but in fact it still is - we didn't terminate the reload/refresh yet) we could perform other calls to "dsdb_schema_refresh" and run into serious trouble (segfault).
2010-07-03s4:schema_set.c - Fix a commentMatthias Dieter Wallnöfer1-1/+2
2010-07-03s4:dsdb_schema_set_attributes - remove unneeded filter criteriasMatthias Dieter Wallnöfer1-2/+4
We already choose the right entry by specifying the right basedn with scope "LDB_SCOPE_BASE".
2010-07-03s4:dsdb_module_load_partition_usn - check for "res->count" equal/unequal to 1Matthias Dieter Wallnöfer1-1/+1
2010-07-03s4:schema_set.c - fix typoMatthias Dieter Wallnöfer1-1/+3
2010-07-03s4:schema_load.c - jump to "failed" on an error conditionMatthias Dieter Wallnöfer1-3/+2
2010-07-03s4:dsdb/tests/passwords.py - set and reset the "minPwdAge" properlyMatthias Dieter Wallnöfer1-2/+21
After a patch proposal of Nadya and some reflection I think that it's really worth to change all tests which need a "0" "minPwdAge" to set it manually and reset the default afterwards. So we can finally introduce the default "minPwdAge" on provision. Patch proposal by: Nadya Ivanova
2010-07-02Tests for user-change-password and force-password-change access rightsNadezhda Ivanova1-4/+242
2010-07-02s4/schema: remove unnecessary deletion of dsdb_schema cached pointerAnatoliy Atanasov1-3/+0
This is needed so we can find and free old schemas based using the cached pointer
2010-07-02s4-dsdb: fixed spelling of supportedSASLMechanismsAndrew Tridgell1-1/+1
Pair-Programmed-With: Andrew Bartlett <abartlet@samba.org>
2010-07-02s4:dsdb Ensure we free old schema copiesAndrew Bartlett1-6/+25
It was reported by aatanasov that we kept around one whole schema per modification made. This does not fix that, but I hope moves us closer to a fix The most important part of the fix is that: - if (schema_out != schema_in) { - talloc_unlink(schema_in, ldb); - } was the wrong way around. This is now handled in the schema_set calls. Andrew Bartlett
2010-07-02s4/dsdb: Assert DSDB_FLAG_*_MODULE is always passed in function callKamen Mazdrashki1-0/+5
Signed-off-by: Andrew Bartlett <abartlet@samba.org>
2010-07-02s4-source4/dsdb/samdb/ldb_modules/util.c Use DSDB_FLAG_NEXT_MODULE flagKamen Mazdrashki1-2/+3
Signed-off-by: Andrew Bartlett <abartlet@samba.org>
2010-07-02s4-source4/dsdb/samdb/ldb_modules/subtree_delete.c: Use ↵Kamen Mazdrashki1-1/+3
DSDB_FLAG_NEXT_MODULE flag Signed-off-by: Andrew Bartlett <abartlet@samba.org>
2010-07-02s4-source4/dsdb/samdb/ldb_modules/schema_load.c: Use DSDB_FLAG_NEXT_MODULE flagKamen Mazdrashki1-1/+2
Signed-off-by: Andrew Bartlett <abartlet@samba.org>
2010-07-02s4-source4/dsdb/samdb/ldb_modules/samldb.c: Use DSDB_FLAG_NEXT_MODULE flagKamen Mazdrashki1-4/+5
Signed-off-by: Andrew Bartlett <abartlet@samba.org>
2010-07-02s4-source4/dsdb/samdb/ldb_modules/samba3sid.c: Use DSDB_FLAG_NEXT_MODULE flagKamen Mazdrashki1-1/+3
Signed-off-by: Andrew Bartlett <abartlet@samba.org>
2010-07-02s4-source4/dsdb/samdb/ldb_modules/rootdse.c: Use DSDB_FLAG_NEXT_MODULE flagKamen Mazdrashki1-2/+3
Signed-off-by: Andrew Bartlett <abartlet@samba.org>
2010-07-02s4-source4/dsdb/samdb/ldb_modules/ridalloc.c: Use DSDB_FLAG_NEXT_MODULE flagKamen Mazdrashki1-1/+1
Signed-off-by: Andrew Bartlett <abartlet@samba.org>
2010-07-02s4-source4/dsdb/samdb/ldb_modules/repl_meta_data.c: Use ↵Kamen Mazdrashki1-4/+5
DSDB_FLAG_NEXT_MODULE flag Signed-off-by: Andrew Bartlett <abartlet@samba.org>
2010-07-02s4-dsdb/samdb/ldb_modules/linked_attributes.c: make use of ↵Kamen Mazdrashki1-2/+2
DSDB_FLAG_NEXT_MODULE flag Signed-off-by: Andrew Bartlett <abartlet@samba.org>
2010-07-02s4/dsdb: Add DSDB_FLAG_NEXT_MODULE flagKamen Mazdrashki1-0/+1
Although it is not currently used in implementation, my intention is for callers to clearly state what action they want to execute. Currently when a caller wants to pass the call to the next module in the chain, this flag is either omitted or 0 is used (which is somewhat hacky, isn't it) Signed-off-by: Andrew Bartlett <abartlet@samba.org>
generated by cgit (git 2.34.1) at 2024-12-21 06:58:50 +0000