freeipa

0 Fork 0

Files

T

Jakub Hrozek 22c3a681da Fine tuning DNS options

Add pointer to self to /etc/hosts to avoid chicken/egg problems when
restarting DNS.

On servers set both dns_lookup_realm and dns_lookup_kdc to false so we don't
attempt to do any resolving. Leave it to true on clients.

Set rdns to false on both server and client.

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

2011-02-14 14:45:22 -05:00

conf

rename static to ui

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

html

error handling style

2011-01-25 16:47:09 -05:00

migration

Fix migration page

2011-02-11 13:28:22 -05:00

Removed 'name' from 'Sudo Command Group name'.

2011-01-24 13:33:00 -05:00

Fine tuning DNS options

2011-02-14 14:45:22 -05:00

tools

Handle bad DM password in ipa-host-net-manage & ipa-copmat-manage.

2011-02-14 10:13:52 -05:00

DNS record search

2011-02-14 13:28:42 -05:00

updates

Add permission/privilege for updating IPA configuration.

2011-02-14 10:22:55 -05:00

configure.ac

rename static to ui

2011-01-20 14:12:47 +00: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.