freeipa

mirror of https://salsa.debian.org/freeipa-team/freeipa.git synced 2025-02-25 18:55:28 -06:00

Files

Christian Heimes b29db07c3b Use os.path.isfile() and isdir()

Replace custom file_exists() and dir_exists() functions with proper
functions from Python's stdlib.

The change also gets rid of pylint's invalid bad-python3-import error,
https://github.com/PyCQA/pylint/issues/1565

Signed-off-by: Christian Heimes <cheimes@redhat.com>
Reviewed-By: Stanislav Laznicka <slaznick@redhat.com>

2017-10-20 12:27:19 +02:00

certmonger

ipa-cacert-manage renew: switch from ext-signed CA to self-signed

2017-10-18 12:34:03 +02:00

conf

Changing cert-find to go through the proxy instead of using the port 8080

2017-06-16 08:56:53 +02:00

html

browser config: cleanup after removal of Firefox extension

2017-09-21 10:27:14 +02:00

migration

logging: do not log into the root logger

2017-07-14 15:55:59 +02:00

oddjob

wsgi, oddjob: remove needless uses of Env

2017-07-14 15:55:59 +02:00

restart_scripts

Fix Certificate renewal (with ext ca)

2017-08-30 12:58:58 +02:00

ds: ignore time skew during initial replication step

2017-10-19 17:48:58 +03:00

tools

Use os.path.isfile() and isdir()

2017-10-20 12:27:19 +02:00

browser config: cleanup after removal of Firefox extension

2017-09-21 10:27:14 +02:00

updates

Adds whoami DS plugin in case that plugin is missing

2017-09-05 14:07:02 +02:00

wsgi

logging: do not log into the root logger

2017-07-14 15:55:59 +02:00

Makefile.am

Configure HTTPD to work via Gss-Proxy

2017-02-15 07:13:37 +01: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.