freeipa

mirror of https://salsa.debian.org/freeipa-team/freeipa.git synced 2026-07-29 23:58:23 -05:00

Files

T

Tomas Babej 75f0801324 Add nfs:NONE to default PAC types only when needed

We need to add nfs:NONE as a default PAC type only if there's no
other default PAC type for nfs. Adds a update plugin which
determines whether default PAC type for nfs is set and adds
nfs:NONE PAC type accordingly.

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

2013-04-15 14:46:21 +02:00

certmonger

Remove unused krbV imports

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

conf

Update mod_wsgi socket directory

2013-03-29 08:59:50 +01:00

ffextension

Kerberos authentication extension makefiles

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

html

Move of Web UI non AMD dep. libs to libs subdirectory

2013-01-18 15:10:36 +01:00

migration

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

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

Pull translation files from Transifex

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

restart_scripts

Do actually stop pki_cad in stop_pkicad instead of starting it.

2013-04-09 16:22:23 +02:00

Remove 'cn' attribute from idnsRecord and idnsZone objectClasses

2013-04-10 13:56:11 +02:00

tools

ipa-server-install: correct help text for --external_{cert,ca}_file

2013-04-15 13:32:58 +02:00

Remove HBAC source hosts from web UI

2013-04-12 14:07:55 -04:00

updates

Add nfs:NONE to default PAC types only when needed

2013-04-15 14:46:21 +02:00

configure.ac

Updated makefiles to build FreeIPA Web UI layer

2013-01-18 15:10:37 +01: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.