freeipa

0 Fork 0

Files

T

Rob Crittenden 1c7261773b Wait for the directory server to come up when updating the agent certificate.

It is possible that either or both of the LDAP instances are being restarted
during the renewal process. Make the script retry if this is the case.

It is also safe to re-run this script if it fails. It will take the current
ipaCert certificate and attempt to update the agent information in LDAP.

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

2012-11-01 13:36:52 -04:00

certmonger

Use DN objects instead of strings

2012-08-12 16:23:24 -04:00

conf

Configure the initial CA as the CRL generator.

2012-10-09 19:24:43 -04:00

ffextension

Kerberos authentication extension makefiles

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

html

Removal of delegation-uris instruction from browser config

2012-10-04 18:35:47 -04:00

migration

Use DN objects instead of strings

2012-08-12 16:23:24 -04:00

Pull translation files from Transifex

2012-10-11 16:09:27 -04:00

restart_scripts

Wait for the directory server to come up when updating the agent certificate.

2012-11-01 13:36:52 -04:00

Explicitly disable betxn plugins for the time being.

2012-10-10 20:24:10 -04:00

tools

Get list of service from LDAP only at startup

2012-11-01 10:58:19 -04:00

Fixed incorrect link to browser config after session expiration

2012-10-24 09:17:26 +02:00

updates

Explicitly disable betxn plugins for the time being.

2012-10-10 20:24:10 -04:00

configure.ac

Kerberos authentication extension makefiles

2012-10-04 18:07:34 -04: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.