Bug 766941

Summary: The full dyndns update message should be logged into debug logs
Product: Red Hat Enterprise Linux 6 Reporter: Jenny Severance <jgalipea>
Component: sssdAssignee: Stephen Gallagher <sgallagh>
Status: CLOSED ERRATA QA Contact: IDM QE LIST <seceng-idm-qe-list>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.2CC: dpal, grajaiya, jgalipea, jhrozek, prc, sgallagh
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: sssd-1.8.0-2.el6.beta2 Doc Type: Bug Fix
Doc Text:
No documentation needed
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-06-20 11:49:44 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Jenny Severance 2011-12-12 20:15:54 UTC
Description of problem:

Right now, the dynamic DNS update message is not logged anywhere. I suspect that the reason for not including it were security concerns.

I think the message should be logged, because the logs are readable by root only anyway and moreover the update message only contains the following data:

    * hostname of the client
    * IP addresses of clients's network interface (either the one the client uses to connect to LDAP or one selected in the sssd config file)
    * client DNS zone
    * Kerberos realm of the client
    * IPA server hostname 

Adding the full nsupdate message would help in debugging dyndns issues as it would be possible to use the same message directly with nsupdate from the command line. 

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


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Upstream ticket :: https://fedorahosted.org/sssd/ticket/893

Comment 1 Stephen Gallagher 2012-01-11 15:09:06 UTC
*** Bug 773326 has been marked as a duplicate of this bug. ***

Comment 4 Jakub Hrozek 2012-04-03 17:53:36 UTC
    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
No documentation needed

Comment 5 Gowrishankar Rajaiyan 2012-05-07 08:31:42 UTC
nsupdate messages are logged after setting debug_level = 6 and above.

relevant sssd.conf:
[domain/lab.eng.pnq.redhat.com]
debug_level = 6
cache_credentials = True
krb5_store_password_if_offline = True
ipa_domain = lab.eng.pnq.redhat.com
id_provider = ipa
auth_provider = ipa
access_provider = ipa
chpass_provider = ipa
ipa_dyndns_update = True
ipa_dyndns_iface = eth0
ipa_server = _srv_, primenova.lab.eng.pnq.redhat.com
ldap_tls_cacert = /etc/ipa/ca.crt


<snip>
(Mon May  7 02:02:54 2012) [sssd[be[lab.eng.pnq.redhat.com]]] [create_nsupdate_message] (0x0400):  -- Begin nsupdate message -- 
server primenova.lab.eng.pnq.redhat.com
realm LAB.ENG.PNQ.REDHAT.COM
zone lab.eng.pnq.redhat.com.
update delete rodimus.lab.eng.pnq.redhat.com. in A
send
update delete rodimus.lab.eng.pnq.redhat.com. in AAAA
send
update add rodimus.lab.eng.pnq.redhat.com. 86400 in AAAA fe80::5054:ff:fe18:57c6
update add rodimus.lab.eng.pnq.redhat.com. 86400 in AAAA 2620:52:0:41c9:5054:ff:fe18:57c6
update add rodimus.lab.eng.pnq.redhat.com. 86400 in A 10.65.201.240
send
(Mon May  7 02:02:54 2012) [sssd[be[lab.eng.pnq.redhat.com]]] [create_nsupdate_message] (0x0400):  -- End nsupdate message -- 
</snip>

Verified in version: sssd-1.8.0-25.el6.x86_64

Comment 7 errata-xmlrpc 2012-06-20 11:49:44 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2012-0747.html