diff options
| author | Samuel Cabrero <scabrero@samba.org> | 2020-06-19 16:31:39 +0200 |
|---|---|---|
| committer | Andrew Bartlett <abartlet@samba.org> | 2021-04-07 09:18:30 +0000 |
| commit | 1e559f958708998324dc4873cccb63899126e5b5 (patch) | |
| tree | b416607ac4c9f7cb37cd0c067d860801e67e348b /selftest | |
| parent | de28d915d7f135c43c35cf2b5167f9603e99b1f6 (diff) | |
| download | samba-1e559f958708998324dc4873cccb63899126e5b5.tar.gz | |
selftest: Test RPC handles and association groups from different connection
Add a test to check if a RPC handle can be used from a different connection
than the one where it was created, when the same association group is
requested in the bind operation of the second connection.
The association group handling is one of the differences between the S3
and S4 RPC server implementations provided by the implementation
callbacks after the merge.
Association groups work fine in the S4 implementation as the RPC server
runs in one process, except for the 'smbd' embedded services provided
by the S3 implementation like winreg (see lp_enforce_ad_dc_settings()).
In the S3 implementation, association groups should work in the same
process, but the merge introduced a bug where a new association group is
always created even when it already exists in the same process.
Signed-off-by: Samuel Cabrero <scabrero@samba.org>
Reviewed-by: Andrew Bartlett <abartlet@samba.org>
Reviewed-by: Andreas Schneider <asn@samba.org>
Diffstat (limited to 'selftest')
| -rw-r--r-- | selftest/knownfail.d/s3-rpc-assoc-groups | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/selftest/knownfail.d/s3-rpc-assoc-groups b/selftest/knownfail.d/s3-rpc-assoc-groups new file mode 100644 index 00000000000..29b1b341561 --- /dev/null +++ b/selftest/knownfail.d/s3-rpc-assoc-groups @@ -0,0 +1 @@ +^samba3.rpc.bind.assoc_group_handles_external\(nt4_dc\) |