freeipa

0 Fork 0

Files

T

Alexander Bokovoy 0840b588d7 Add cifs principal to S4U2Proxy targets only when running ipa-adtrust-install

Since CIFS principal is generated by ipa-adtrust-install and is only
usable after setting CIFS configuration, there is no need to include it
into default setup.

This should fix upgrades from 2.2 to 3.0 where CIFS principal does not
exist by default.

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

2012-10-09 18:15:01 -04:00

certmonger

Use DN objects instead of strings

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

conf

Move CRL publish directory to IPA owned directory

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

Update the pot file (translation source)

2012-09-12 22:04:16 -04:00

restart_scripts

Use Dogtag 10 only when it is available

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

Add cifs principal to S4U2Proxy targets only when running ipa-adtrust-install

2012-10-09 18:15:01 -04:00

tools

Fix CA CRL migration crash in ipa-upgradeconfig

2012-10-10 14:15:46 +02:00

support multi-line error messages in exceptions

2012-10-09 10:18:40 +02:00

updates

Add cifs principal to S4U2Proxy targets only when running ipa-adtrust-install

2012-10-09 18:15:01 -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.