8:19 a.m.
Hi,
I am working on getting the logging for FreeIPA set-up properly.
I have a test server (testy) running.
This server/host is under control of FreeIPA.
I have a user group defined for test users, and a host group for test servers.
There is a HBAC rule to ensure that the members of testing group has only access to the
test servers.
This works fine, but I have a question regarding the logs.
Scenario 1:
User : test2 is member of the testusergroup and should be granted access to the test
server.
This works as expected, test2 is authorized to login to server and the log
(var/log/krb5kdc.log) looks like this.
Sep 18 14:55:19 idm1.myrealm.net krb5kdc[287272](info): AS_REQ (8 etypes
{aes256-cts-hmac-sha1-96(18), aes128-cts-hmac-sha1-96(17), aes256-cts-hmac-sha384-192(20),
aes128-cts-hmac-sha256-128(19), UNSUPPORTED:des3-hmac-sha1(16),
DEPRECATED:arcfour-hmac(23), camellia128-cts-cmac(25), camellia256-cts-cmac(26)})
my.ip.adress.xx: NEEDED_PREAUTH: test2(a)MYREALM.NET for krbtgt/MYREALM.NET(a)MYREALM.NET,
Additional pre-authentication required
Sep 18 14:55:19 idm1.myrealm.net krb5kdc[287272](info): closing down fd 11
Sep 18 14:55:19 idm1.myrealm.net krb5kdc[287272](info): AS_REQ (8 etypes
{aes256-cts-hmac-sha1-96(18), aes128-cts-hmac-sha1-96(17), aes256-cts-hmac-sha384-192(20),
aes128-cts-hmac-sha256-128(19), UNSUPPORTED:des3-hmac-sha1(16),
DEPRECATED:arcfour-hmac(23), camellia128-cts-cmac(25), camellia256-cts-cmac(26)})
my.ip.adress.xx: NEEDED_PREAUTH: test2(a)MYREALM.NET for krbtgt/MYREALM.NET(a)MYREALM.NET,
Additional pre-authentication required
Sep 18 14:55:19 idm1.myrealm.net krb5kdc[287272](info): closing down fd 11
Sep 18 14:55:19 idm1.myrealm.net krb5kdc[287271](info): AS_REQ (8 etypes
{aes256-cts-hmac-sha1-96(18), aes128-cts-hmac-sha1-96(17), aes256-cts-hmac-sha384-192(20),
aes128-cts-hmac-sha256-128(19), UNSUPPORTED:des3-hmac-sha1(16),
DEPRECATED:arcfour-hmac(23), camellia128-cts-cmac(25), camellia256-cts-cmac(26)})
my.ip.adress.xx: ISSUE: authtime 1695041719, etypes {rep=aes256-cts-hmac-sha1-96(18),
tkt=aes256-cts-hmac-sha384-192(20), ses=aes256-cts-hmac-sha1-96(18)}, test2(a)MYREALM.NET
for krbtgt/MYREALM.NET(a)MYREALM.NET
Sep 18 14:55:19 idm1.myrealm.net krb5kdc[287271](info): closing down fd 11
Sep 18 14:55:19 idm1.myrealm.net krb5kdc[287271](info): TGS_REQ (8 etypes
{aes256-cts-hmac-sha1-96(18), aes128-cts-hmac-sha1-96(17), aes256-cts-hmac-sha384-192(20),
aes128-cts-hmac-sha256-128(19), UNSUPPORTED:des3-hmac-sha1(16),
DEPRECATED:arcfour-hmac(23), camellia128-cts-cmac(25), camellia256-cts-cmac(26)})
my.ip.adress.xx: ISSUE: authtime 1695041719, etypes {rep=aes256-cts-hmac-sha1-96(18),
tkt=aes256-cts-hmac-sha384-192(20), ses=aes256-cts-hmac-sha1-96(18)}, test2(a)MYREALM.NET
for host/testy.myrealm.net(a)MYREALM.NET
Sep 18 14:55:19 idm1.myrealm.net krb5kdc[287271](info): closing down fd 11
In this log, I see the AS_REQs and then the TGS_REQ for obtaining the TGS.
Scenario 2:
User : test2 is not a member of testusergroup anymore and should not be granted access to
the test server.
This also works as expected, when logging in with correct password, test2 is denied
service with message "Connection closed by ...."
This is great, but I would like to see this happening in the log:
The log looks like this:
Sep 18 14:58:09 idm1.myrealm.net krb5kdc[287271](info): AS_REQ (8 etypes
{aes256-cts-hmac-sha1-96(18), aes128-cts-hmac-sha1-96(17), aes256-cts-hmac-sha384-192(20),
aes128-cts-hmac-sha256-128(19), UNSUPPORTED:des3-hmac-sha1(16),
DEPRECATED:arcfour-hmac(23), camellia128-cts-cmac(25), camellia256-cts-cmac(26)})
my.ip.adress.xx: NEEDED_PREAUTH: test2(a)MYREALM.NET for krbtgt/MYREALM.NET(a)MYREALM.NET,
Additional pre-authentication required
Sep 18 14:58:09 idm1.myrealm.net krb5kdc[287271](info): closing down fd 11
Sep 18 14:58:09 idm1.myrealm.net krb5kdc[287272](info): AS_REQ (8 etypes
{aes256-cts-hmac-sha1-96(18), aes128-cts-hmac-sha1-96(17), aes256-cts-hmac-sha384-192(20),
aes128-cts-hmac-sha256-128(19), UNSUPPORTED:des3-hmac-sha1(16),
DEPRECATED:arcfour-hmac(23), camellia128-cts-cmac(25), camellia256-cts-cmac(26)})
my.ip.adress.xx: NEEDED_PREAUTH: test2(a)MYREALM.NET for krbtgt/MYREALM.NET(a)MYREALM.NET,
Additional pre-authentication required
Sep 18 14:58:09 idm1.myrealm.net krb5kdc[287272](info): closing down fd 11
Sep 18 14:58:09 idm1.myrealm.net krb5kdc[287271](info): AS_REQ (8 etypes
{aes256-cts-hmac-sha1-96(18), aes128-cts-hmac-sha1-96(17), aes256-cts-hmac-sha384-192(20),
aes128-cts-hmac-sha256-128(19), UNSUPPORTED:des3-hmac-sha1(16),
DEPRECATED:arcfour-hmac(23), camellia128-cts-cmac(25), camellia256-cts-cmac(26)})
my.ip.adress.xx: ISSUE: authtime 1695041889, etypes {rep=aes256-cts-hmac-sha1-96(18),
tkt=aes256-cts-hmac-sha384-192(20), ses=aes256-cts-hmac-sha1-96(18)}, test2(a)MYREALM.NET
for krbtgt/MYREALM.NET(a)MYREALM.NET
Sep 18 14:58:09 idm1.myrealm.net krb5kdc[287271](info): closing down fd 11
Sep 18 14:58:09 idm1.myrealm.net krb5kdc[287272](info): TGS_REQ (8 etypes
{aes256-cts-hmac-sha1-96(18), aes128-cts-hmac-sha1-96(17), aes256-cts-hmac-sha384-192(20),
aes128-cts-hmac-sha256-128(19), UNSUPPORTED:des3-hmac-sha1(16),
DEPRECATED:arcfour-hmac(23), camellia128-cts-cmac(25), camellia256-cts-cmac(26)})
my.ip.adress.xx: ISSUE: authtime 1695041889, etypes {rep=aes256-cts-hmac-sha1-96(18),
tkt=aes256-cts-hmac-sha384-192(20), ses=aes256-cts-hmac-sha1-96(18)}, test2(a)MYREALM.NET
for host/testy.myrealm.net(a)MYREALM.NET
Sep 18 14:58:09 idm1.myrealm.net krb5kdc[287272](info): closing down fd 11
In this log, I see the same AS_REQ as expected with no failure, since I am using correct
password , and the same kind of TGS_REQ
My question is:
When FreeIPA is handling the service authorization through the use of HBAC rules, why does
it issue a similar TGS?
Or is it different?,
How does the actual authorization fail between the client and the server/service itself?
Is it the content of the TGS ?
I know I can see failed login in the logs of the server it self, but I would like to see
everything that goes on in the FreeIPA logs.
regards
Ole Frøslie
Com4