<feed xmlns='http://www.w3.org/2005/Atom'>
<title>sssd2.git/src/providers, branch master</title>
<subtitle>System Security Services Daemon [okos' clone]</subtitle>
<link rel='alternate' type='text/html' href='https://fedorapeople.org/cgit/okos/public_git/sssd2.git/'/>
<entry>
<title>Only check UPN if enterprise principals are not used</title>
<updated>2013-05-03T19:02:10+00:00</updated>
<author>
<name>Jakub Hrozek</name>
<email>jhrozek@redhat.com</email>
</author>
<published>2013-05-03T17:30:51+00:00</published>
<link rel='alternate' type='text/html' href='https://fedorapeople.org/cgit/okos/public_git/sssd2.git/commit/?id=42084c0f500ba849393b0e87477cd1af397ddecb'/>
<id>42084c0f500ba849393b0e87477cd1af397ddecb</id>
<content type='text'>
If enterprise principals are enabled (which is the default in the AD
provider), then the returned UPN might be slightly different from
the one SSSD constructs before attempting the login. This patch makes
SSSD only check if the principal is the same when the enterprise
principals are disabled.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
If enterprise principals are enabled (which is the default in the AD
provider), then the returned UPN might be slightly different from
the one SSSD constructs before attempting the login. This patch makes
SSSD only check if the principal is the same when the enterprise
principals are disabled.
</pre>
</div>
</content>
</entry>
<entry>
<title>AD: Always initialize ID mapping</title>
<updated>2013-05-03T19:02:04+00:00</updated>
<author>
<name>Jakub Hrozek</name>
<email>jhrozek@redhat.com</email>
</author>
<published>2013-05-03T14:00:37+00:00</published>
<link rel='alternate' type='text/html' href='https://fedorapeople.org/cgit/okos/public_git/sssd2.git/commit/?id=2e4f8db631a10224dac20e8a472f751fef0e3fcd'/>
<id>2e4f8db631a10224dac20e8a472f751fef0e3fcd</id>
<content type='text'>
Because we now always store SIDs in the LDAP provider, we also need to
always initialize the ID mapping context even if ID mapping itself is
off.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Because we now always store SIDs in the LDAP provider, we also need to
always initialize the ID mapping context even if ID mapping itself is
off.
</pre>
</div>
</content>
</entry>
<entry>
<title>Active Directory dynamic DNS updates</title>
<updated>2013-05-03T18:31:39+00:00</updated>
<author>
<name>Jakub Hrozek</name>
<email>jhrozek@redhat.com</email>
</author>
<published>2013-04-16T15:04:43+00:00</published>
<link rel='alternate' type='text/html' href='https://fedorapeople.org/cgit/okos/public_git/sssd2.git/commit/?id=74e95cfd9d3939dfe9417d79d2f6fc79b361405f'/>
<id>74e95cfd9d3939dfe9417d79d2f6fc79b361405f</id>
<content type='text'>
https://fedorahosted.org/sssd/ticket/1504

Implements dynamic DNS updates for the AD provider. By default, the
updates also update the reverse zone and run periodically every 24
hours.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
https://fedorahosted.org/sssd/ticket/1504

Implements dynamic DNS updates for the AD provider. By default, the
updates also update the reverse zone and run periodically every 24
hours.
</pre>
</div>
</content>
</entry>
<entry>
<title>Split out the common code from timed DNS updates</title>
<updated>2013-05-03T18:31:38+00:00</updated>
<author>
<name>Jakub Hrozek</name>
<email>jhrozek@redhat.com</email>
</author>
<published>2013-04-30T16:55:29+00:00</published>
<link rel='alternate' type='text/html' href='https://fedorapeople.org/cgit/okos/public_git/sssd2.git/commit/?id=33df734b39538eeb870b118b7feea76f90bb004b'/>
<id>33df734b39538eeb870b118b7feea76f90bb004b</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>dyndns: new option dyndns_auth</title>
<updated>2013-05-03T18:25:46+00:00</updated>
<author>
<name>Jakub Hrozek</name>
<email>jhrozek@redhat.com</email>
</author>
<published>2013-04-16T13:11:38+00:00</published>
<link rel='alternate' type='text/html' href='https://fedorapeople.org/cgit/okos/public_git/sssd2.git/commit/?id=e15a9f81eb33066937710d7dee6976a3646d119c'/>
<id>e15a9f81eb33066937710d7dee6976a3646d119c</id>
<content type='text'>
This options is mostly provided for future expansion. Currently it is
undocumented and both IPA and AD dynamic DNS updates default to
GSS-TSIG. Allowed values are GSS-TSIG and none.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
This options is mostly provided for future expansion. Currently it is
undocumented and both IPA and AD dynamic DNS updates default to
GSS-TSIG. Allowed values are GSS-TSIG and none.
</pre>
</div>
</content>
</entry>
<entry>
<title>dyndns: new option dyndns_force_tcp</title>
<updated>2013-05-03T18:25:46+00:00</updated>
<author>
<name>Jakub Hrozek</name>
<email>jhrozek@redhat.com</email>
</author>
<published>2013-04-16T12:19:15+00:00</published>
<link rel='alternate' type='text/html' href='https://fedorapeople.org/cgit/okos/public_git/sssd2.git/commit/?id=e45b81abe0aafa8a04bd64ac31a2fac63ce675b7'/>
<id>e45b81abe0aafa8a04bd64ac31a2fac63ce675b7</id>
<content type='text'>
https://fedorahosted.org/sssd/ticket/1831

Adds a new option that can be used to force nsupdate to only use TCP to
communicate with the DNS server.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
https://fedorahosted.org/sssd/ticket/1831

Adds a new option that can be used to force nsupdate to only use TCP to
communicate with the DNS server.
</pre>
</div>
</content>
</entry>
<entry>
<title>dyndns: New option dyndns_update_ptr</title>
<updated>2013-05-03T18:25:46+00:00</updated>
<author>
<name>Jakub Hrozek</name>
<email>jhrozek@redhat.com</email>
</author>
<published>2013-04-30T14:40:09+00:00</published>
<link rel='alternate' type='text/html' href='https://fedorapeople.org/cgit/okos/public_git/sssd2.git/commit/?id=38ebc764eeb7693e0c4f0894d6687e54fbba871b'/>
<id>38ebc764eeb7693e0c4f0894d6687e54fbba871b</id>
<content type='text'>
https://fedorahosted.org/sssd/ticket/1832

While some servers, such as FreeIPA allow the PTR record to be
synchronized when the forward record is updated, other servers,
including Active Directory, require that the PTR record is synchronized
manually.

This patch adds a new option, dyndns_update_ptr that automatically
generates appropriate DNS update message for updating the reverse zone.

This option is off by default in the IPA provider.

Also renames be_nsupdate_create_msg to be_nsupdate_create_fwd_msg
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
https://fedorahosted.org/sssd/ticket/1832

While some servers, such as FreeIPA allow the PTR record to be
synchronized when the forward record is updated, other servers,
including Active Directory, require that the PTR record is synchronized
manually.

This patch adds a new option, dyndns_update_ptr that automatically
generates appropriate DNS update message for updating the reverse zone.

This option is off by default in the IPA provider.

Also renames be_nsupdate_create_msg to be_nsupdate_create_fwd_msg
</pre>
</div>
</content>
</entry>
<entry>
<title>dyndns: new option dyndns_refresh_interval</title>
<updated>2013-05-03T18:25:46+00:00</updated>
<author>
<name>Jakub Hrozek</name>
<email>jhrozek@redhat.com</email>
</author>
<published>2013-04-09T15:40:40+00:00</published>
<link rel='alternate' type='text/html' href='https://fedorapeople.org/cgit/okos/public_git/sssd2.git/commit/?id=5a4239490c7fb7d732180a9d40f27f0247c56631'/>
<id>5a4239490c7fb7d732180a9d40f27f0247c56631</id>
<content type='text'>
This new options adds the possibility of updating the DNS entries
periodically regardless if they have changed or not. This feature
will be useful mainly in AD environments where the Windows clients
periodically update their DNS records.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
This new options adds the possibility of updating the DNS entries
periodically regardless if they have changed or not. This feature
will be useful mainly in AD environments where the Windows clients
periodically update their DNS records.
</pre>
</div>
</content>
</entry>
<entry>
<title>Convert IPA-specific options to be back-end agnostic</title>
<updated>2013-05-03T18:22:37+00:00</updated>
<author>
<name>Jakub Hrozek</name>
<email>jhrozek@redhat.com</email>
</author>
<published>2013-04-09T12:20:28+00:00</published>
<link rel='alternate' type='text/html' href='https://fedorapeople.org/cgit/okos/public_git/sssd2.git/commit/?id=04868f1573f4b26ef34610b6d7069172f93bd8ab'/>
<id>04868f1573f4b26ef34610b6d7069172f93bd8ab</id>
<content type='text'>
This patch introduces new options for dynamic DNS updates that are not
specific to any back end. The current ipa dyndns options are still
usable, just with a deprecation warning.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
This patch introduces new options for dynamic DNS updates that are not
specific to any back end. The current ipa dyndns options are still
usable, just with a deprecation warning.
</pre>
</div>
</content>
</entry>
<entry>
<title>Refactor dynamic DNS updates</title>
<updated>2013-05-03T18:22:29+00:00</updated>
<author>
<name>Jakub Hrozek</name>
<email>jhrozek@redhat.com</email>
</author>
<published>2013-03-26T15:49:26+00:00</published>
<link rel='alternate' type='text/html' href='https://fedorapeople.org/cgit/okos/public_git/sssd2.git/commit/?id=9cb46bc62f22e0104f1b41a423b014c281ef5fc2'/>
<id>9cb46bc62f22e0104f1b41a423b014c281ef5fc2</id>
<content type='text'>
Provides two new layers instead of the previous IPA specific layer:
 1) dp_dyndns.c -- a very generic dyndns layer on the DP level. Its
 purpose it to make it possible for any back end to use dynamic DNS
 updates.
 2) sdap_dyndns.c -- a wrapper around dp_dyndns.c that utilizes some
 LDAP-specific features like autodetecting the address from the LDAP
 connection.

Also converts the dyndns code to new specific error codes.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Provides two new layers instead of the previous IPA specific layer:
 1) dp_dyndns.c -- a very generic dyndns layer on the DP level. Its
 purpose it to make it possible for any back end to use dynamic DNS
 updates.
 2) sdap_dyndns.c -- a wrapper around dp_dyndns.c that utilizes some
 LDAP-specific features like autodetecting the address from the LDAP
 connection.

Also converts the dyndns code to new specific error codes.
</pre>
</div>
</content>
</entry>
</feed>
