freeipa.git/install/tools/ipa-server-install, branch webui-details

This patch removes the existing UI functionality, as a prep for adding the Javascript based ui.

2010-07-29T14:44:56+00:00

Create default HBAC rule allowing any user to access any host from any host

2010-05-05T18:57:58+00:00

This is to make initial installation and testing easier.

Use the --no_hbac_allow option on the command-line to disable this when
doing an install.

To remove it from a running server do: ipa hbac-del allow_all

Make the installer/uninstaller more aware of its state

2010-05-03T19:41:18+00:00

We have had a state file for quite some time that is used to return
the system to its pre-install state. We can use that to determine what
has been configured.

This patch:
- uses the state file to determine if dogtag was installed
- prevents someone from trying to re-install an installed server
- displays some output when uninstalling
- re-arranges the ipa_kpasswd installation so the state is properly saved
- removes pkiuser if it was added by the installer
- fetches and installs the CA on both masters and clients

Fix a couple of syntax errors in the installer.

2010-04-27T21:51:13+00:00

I meant to push these along with the original patch but pushed the wrong one.

Replace a new instance of IPAdmin use in ipa-server-install.

2010-04-27T20:29:36+00:00

Connect to the ldap during the uninstallation

2010-04-23T21:19:36+00:00

We need to ask the user for a password and connect to the ldap so the
bind uninstallation procedure can remove old records. This is of course
only helpful if one has more than one IPA server configured.

Fix installing IPA with an external CA

2010-04-23T10:57:34+00:00

- cache all interactive answers
- set non-interactive to True for the second run so nothing is asked
- convert boolean values that are read in
- require absolute paths for the external CA and signed cert files
- fix the invocation message for the second ipa-server-install run

Use ldap2 instead of legacy LDAP code from v1 in installer scripts.

2010-04-19T15:27:10+00:00

Better customize the message regarding the CA based on the install options.

2010-03-19T10:55:33+00:00

There are now 3 cases:

- Install a dogtag CA and issue server certs using that
- Install a selfsign CA and issue server certs using that
- Install using either dogtag or selfsign and use the provided PKCS#12 files
  for the server certs. The installed CA will still be used by the cert
  plugin to issue any server certs.

Retrieve the LDAP schema using kerberos credentials.

2010-03-18T05:36:53+00:00

This is required so we can disable anonymous access in 389-ds.