IntenseWebs/freeipa
3
0
Fork 0
mirror of https://salsa.debian.org/freeipa-team/freeipa.git synced 2025-01-16 19:31:55 -06:00
Code Issues Packages Projects Releases Wiki Activity
5b968f9632
freeipa/install
History
Martin Kosek 5b968f9632 Improve ipa-replica-prepare DNS check 
Currently, verify_fqdn() function raises RuntimeError for every
problem with the hostname. This makes it difficult for tools
like ipa-replica-prepare to behave differently for a subset of
raised errors (for example to be able to create a DNS record for
new replica when verify_fqdn() reports a lookup error).

Implement own exceptions for verify_fqdn() that they can be safely
used to distinguish the error type.

https://fedorahosted.org/freeipa/ticket/1899
2011-10-06 11:27:50 +02:00
..
conf Revert "Always require SSL in the Kerberos authorization block." 2011-09-27 08:54:42 +02:00
html Fixed browser configuration pages 2011-08-17 17:28:25 +00:00
migration Migration: don't assume there is only one naming context, add logging. 2011-10-04 16:14:11 +02:00
po 25 Create Tool for Enabling/Disabling Managed Entry Plugins 2011-09-21 09:22:13 +02:00
share list users from nested groups, too 2011-10-05 09:06:42 +02:00
tools Improve ipa-replica-prepare DNS check 2011-10-06 11:27:50 +02:00
ui Added selectable labels for radio buttons. 2011-10-05 15:08:07 +02:00
updates The precendence on the modrdn plugin was set in the wrong location. 2011-09-13 17:36:59 +02: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.