freeipa

mirror of https://salsa.debian.org/freeipa-team/freeipa.git synced 2026-07-29 23:58:23 -05:00

Files

T

Tomas Babej 6839483d29 Enforce host existence only where needed in ipa-replica-manage

In ipa-replica-manage commands, we enforce that hostnames we work
with are resolvable. However, this caused errors while deleting
or disconnecting a ipa / winsync replica, if that replica was down
and authoritative server for itself.

Also adds an --no-lookup flag to disable host existence checks.

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

2013-05-02 10:53:15 -04:00

certmonger

Remove unused krbV imports

2013-02-01 08:13:17 +01:00

conf

Update mod_wsgi socket directory

2013-03-29 08:59:50 +01:00

ffextension

Kerberos authentication extension makefiles

2012-10-04 18:07:34 -04:00

html

Move of Web UI non AMD dep. libs to libs subdirectory

2013-01-18 15:10:36 +01:00

migration

Use IPAdmin rather than raw python-ldap in migration.py and ipadiscovery.py

2013-03-13 12:36:33 +01:00

Update translations from Transifex

2013-04-15 18:46:27 +02:00

restart_scripts

Do actually stop pki_cad in stop_pkicad instead of starting it.

2013-04-09 16:22:23 +02:00

Fix syntax errors in schema files

2013-04-26 11:15:16 -04:00

tools

Enforce host existence only where needed in ipa-replica-manage

2013-05-02 10:53:15 -04:00

Fix: Certificate status is not visible in Service and Host page

2013-04-30 17:30:15 +02:00

updates

Fix syntax errors in schema files

2013-04-26 11:15:16 -04:00

configure.ac

Updated makefiles to build FreeIPA Web UI layer

2013-01-18 15:10:37 +01:00

Makefile.am

Move CRL publish directory to IPA owned directory

2012-10-09 16:00:01 +02: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.