freeipa.git/ipa-client/ipaclient, branch gssapi-delegate

Make sure that hostname specified by user is not an IP address.

2011-07-25T05:47:52+00:00

ticket 1375

Make ipa-client-install error messages more understandable and relevant.

2011-07-20T00:41:54+00:00

* Check remote LDAP server to see if it is a V2 server
* Replace numeric return values with alphanumeric constants
* Display the error message from the ipa-enrollment extended op
* Remove generic join failed error message when XML-RPC fails
* Don't display Certificate subject base when enrollment fails
* Return proper error message when LDAP bind fails

https://fedorahosted.org/freeipa/ticket/1417

KDC autodiscovery may fail when domain is not realm

2011-05-17T06:56:22+00:00

When ipa-client-install autodiscovers IPA server values it
doesn't fill the fixed KDC address to Kerberos configuration
file. However, when realm != domain or the autodiscovered values
are overridden, installation may fail because it cannot find the
KDC.

This patch adds a failover to use static KDC address in case when
such an issue occurs.

https://fedorahosted.org/freeipa/ticket/1100

Fix lint false positives.

2011-04-13T13:58:45+00:00

Make retrieval of the CA during DNS discovery non-fatal.

2011-03-30T14:03:56+00:00

ticket 1135

18 Use TLS for ipadiscovery during ipa-client-install https://fedorahosted.org/freeipa/ticket/974

2011-02-21T21:09:37+00:00

Change FreeIPA license to GPLv3+

2010-12-20T22:19:53+00:00

The changes include:
 * Change license blobs in source files to mention GPLv3+ not GPLv2 only
 * Add GPLv3+ license text
 * Package COPYING not LICENSE as the license blobs (even the old ones)
   mention COPYING specifically, it is also more common, I think

 https://fedorahosted.org/freeipa/ticket/239

Better distinguish between when DNS discovery works and search more domains.

2010-09-20T20:04:30+00:00

Passing domain and server on the command-line used to be considered as
DNS autodiscovery worked. This was problematic if there was in fact no
SRV records because krb5.conf would be configured without a specific KDC
causing all Kerberos ops to fail.

Now if you pass in a domain/server it still tries to see if they are
discoverable and if so won't hardcode a server, but will fall back to doing
so if necessary.

Also be a lot more aggressive on looking for the SRV records. Use the
search and domain values from /etc/resolv.conf on the chance that the
SRV records aren't in the domain of the hostname of the machine.

An example of this would be if your laptop is in dhcp.example.com and
your company's SRV records are in corp.example.com. Searching
dhcp.example.com and example.com won't find the SRV records but the user
is likely to have corp.redhat.com in the search list, at least.

ticket 234

Better LDAP error handling in ipa-client-install

2009-12-01T16:52:14+00:00

Clean up additional issues discovered with pylint and pychecker

2009-08-20T13:20:56+00:00