freeipa

0 Fork 0

Files

T

Rob Crittenden 6e1a806709 Improve error messages in ipa-replica-manage.

Correctly handle case where we bind using GSSAPI with an unauthorized user.

Remove extraneous except clause. We now have handle for LDAP errors.

Make it explicit in a few places what server we can't connect to.

When the remote replica is down and we are forcing its removal, remove
a duplicate entry from the list of servers to remove.

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

2012-10-23 14:11:50 -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

Use Dogtag 10 only when it is available

2012-09-17 18:43:59 -04:00

Explicitly disable betxn plugins for the time being.

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

tools

Improve error messages in ipa-replica-manage.

2012-10-23 14:11:50 -04:00

Simpler instructions to generate certificate

2012-10-19 14:30:06 +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.