Bug 1080130 - No User Event Log Generated in AD
Summary: No User Event Log Generated in AD
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: sssd
Version: 20
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jakub Hrozek
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-03-24 18:01 UTC by bkuhn
Modified: 2014-03-24 19:36 UTC (History)
8 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-03-24 18:33:14 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
sssd.conf (686 bytes, text/plain)
2014-03-24 18:01 UTC, bkuhn
no flags Details

Description bkuhn 2014-03-24 18:01:28 UTC
Created attachment 878135 [details]
sssd.conf

Description of problem:
When logging in as Active Directory user no event logs are generated for successful or failed login.


Version-Release number of selected component (if applicable):
sssd-1.11.4-1

How reproducible:
Every time

Steps to Reproduce:
1. Log in to Fedora 20 with Active Directory credentials
2. Check domain controllers for account success/failure
3. Nothing there

Actual results:
Nothing

Expected results:
An event log of either success or failure

Additional info:
Fedora 20 configured to authenticate to Windows 2008 r2 domain. Login with same account on windows workstation and logon success/failures appear.

There is data in /var/log/secure show success/failures of the ad account.

Comment 1 Dmitri Pal 2014-03-24 18:33:14 UTC
Then SSSD was most likely not able to access your AD and authenticated offline. Please check SSSD debug logs for more details.

You can also turn off the offline authentication in sssd.conf and observe failures to authenticate if the AD is not reachable.

This is not an SSSD issue.

Comment 2 Sumit Bose 2014-03-24 19:36:28 UTC
Please also check the journalctl output for messages from pam_sss. Since Fedora 20 the systemd journal is the default logging mechanism and the classic log files are not used anymore. 

You can install the rsyslog package to get messages into the classic log files as well.


Note You need to log in before you can comment on or make changes to this bug.