freeipa

0 Fork 0

Files

T

Fraser Tweedale 39fdc2d250 ipa_certupdate: avoid classmethod and staticmethod

Because classmethod and staticmethod are just fancy ways of calling
plain old functions, turn the classmethods and staticmethods of
CertUpdate into plain old functions.

This improves readability by making it clear that the behaviour of
the routines cannot depend on instance or class variables.

Part of: https://pagure.io/freeipa/issue/6577

Reviewed-By: Rob Crittenden <rcritten@redhat.com>

2017-12-11 08:35:04 +01:00

certmonger

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

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

conf

Require UTF-8 fs encoding

2017-11-21 16:13:28 +01: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

renew_ra_cert: fix update of IPA RA user entry

2017-12-07 17:28:12 +01:00

Require UTF-8 fs encoding

2017-11-21 16:13:28 +01:00

tools

ipa_certupdate: avoid classmethod and staticmethod

2017-12-11 08:35:04 +01:00

WebUI: make Domain Resolution Order writable

2017-11-16 19:54:49 +02:00

updates

Add indexing to improve host-find performance

2017-11-07 16:49:36 +01: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.