auth_log testing
Gary Lockyer
gary at catalyst.net.nz
Tue Nov 7 18:34:16 UTC 2017
On 08/11/17 02:23, Andreas Schneider via samba-technical wrote:
> On Monday, 6 November 2017 19:06:04 CET Gary Lockyer via samba-technical
> wrote:
>> The auth logging code is making standard samba debug calls so it should
>> be going to the samba logs.
>>
>> The log levels are:
>>
>> 2 - log authentication failures
>> 3 - successful authentications
>> 4 - successful authorisations
>> 5 - Anonymous authentications and authorisations.
>>
>> Alternatively the following Debug classes exist.
>> DBGC_AUTH_AUDIT 24
>> DBGC_AUTH_AUDIT_JSON 25
>
> Well, that's the problem. The MIT KDC is a different process!
>
>> Also the events get sent via the messaging api, which is how the tests work.
>
> Well, the MIT KDC is its own process loading the Samba KDB module. If the
> tests register only for messaging form samba then they do not get it from the
> KDC process.
The tests use the samba python messaging code, take a look in
python/samba/tests/auth_log_base.py.
>
>
> Andreas
>
Gary
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: OpenPGP digital signature
URL: <http://lists.samba.org/pipermail/samba-technical/attachments/20171108/f0bccac4/signature.sig>
More information about the samba-technical
mailing list