freeipa

0 Fork 0

Files

T

Martin Kosek 77cc5e0246 Hostname used by IPA must be a system hostname

Make sure that the hostname IPA uses is a system hostname. If user
passes a non-system hostname, update the network settings and
system hostname in the same way that ipa-client-install does.

This step should prevent various services failures which may not
be ready to talk to IPA with non-system hostname.

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

2011-10-13 00:54:41 -04:00

conf

Revert "Always require SSL in the Kerberos authorization block."

2011-09-27 08:54:42 +02:00

html

Fixed links to images in config and migration pages

2011-10-06 23:24:12 -05:00

migration

Fixed links to images in config and migration pages

2011-10-06 23:24:12 -05:00

Ticket 1718 - Fix Spanish po translation file

2011-10-11 22:46:02 -04:00

Remove more redundant configuration values from krb5.conf.

2011-10-11 22:00:50 -04:00

tools

Hostname used by IPA must be a system hostname

2011-10-13 00:54:41 -04:00

Fix dynamic display of UI tabs based on rights

2011-10-12 23:19:54 -04:00

updates

updates: Change default limits on ldap searches

2011-10-12 22:42:03 -04:00

configure.ac

ticket 1650 - compute accurate translation statistics

2011-08-18 14:25:58 +02:00

Makefile.am

rename static to ui

2011-01-20 14:12:47 +00:00

README.schema

Add some basic rules for adding new schema

2010-08-27 13:40:37 -04:00

README.schema

Ground rules on adding new schema

Brand new schema, particularly when written specifically for IPA, should be
added in share/*.ldif. Any new files need to be explicitly loaded in
ipaserver/install/dsinstance.py. These simply get copied directly into
the new instance schema directory.

Existing schema (e.g. in an LDAP draft) may either be added as a separate
ldif in share or as an update in the updates directory. The advantage of
adding the schema as an update is if 389-ds ever adds the schema then the
installation won't fail due to existing schema failing to load during
bootstrap.

If the new schema requires a new container then this should be added
to install/bootstrap-template.ldif.