freeipa

0 Fork 0

Files

T

Tomas Babej 45e310ecc4 ipa-adtrust-install: Add warning that we will break existing samba configuration

In case /etc/samba/smb.conf exists and it was not created by ipa-adtrust-install,
print a warning that we will break existing samba configuration and ask for
a confirmation in the interactive mode.

Part of: https://fedorahosted.org/freeipa/ticket/3479

2013-10-14 11:11:17 +02:00

certmonger

Remove unused krbV imports

2013-02-01 08:13:17 +01:00

conf

Do not redirect to https in /ipa/ui on non-HTML files

2013-06-26 15:02:13 +02:00

ffextension

Kerberos authentication extension makefiles

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

html

Make ssbrowser.html work in IE 10

2013-06-04 12:24:13 +02:00

migration

Use IPAdmin rather than raw python-ldap in migration.py and ipadiscovery.py

2013-03-13 12:36:33 +01:00

Update translations from Transifex

2013-10-04 14:51:19 +02:00

restart_scripts

Make CS.cfg edits with CA instance stopped

2013-08-26 16:21:36 +02:00

Remove --no-serial-autoincrement

2013-10-11 09:47:59 +02:00

tools

ipa-adtrust-install: Add warning that we will break existing samba configuration

2013-10-14 11:11:17 +02:00

Fix enablement of automount map type selector

2013-10-03 09:13:45 +02:00

updates

Remove faulty DNS memberOf Task

2013-10-04 14:30:13 +02:00

wsgi

Generate plugin index dynamically

2013-05-06 16:22:30 +02:00

configure.ac

Prevent *.pyo and *.pyc multilib problems

2013-08-13 15:31:46 +02:00

Makefile.am

Change group ownership of CRL publish directory

2013-07-16 12:17:40 +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.