freeipa

mirror of https://salsa.debian.org/freeipa-team/freeipa.git synced 2025-02-25 18:55:28 -06:00

Files

Tomas Babej ddb3957011 Add ipaRangeType attribute to LDAP Schema

This adds a new LDAP attribute ipaRangeType with
OID 2.16.840.1.113730.3.8.11.41 to the LDAP Schema.

ObjectClass ipaIDrange has been altered to require
ipaRangeType attribute.

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

2013-06-10 12:27:33 +03:00

certmonger

Remove unused krbV imports

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

conf

Generate plugin index dynamically

2013-05-06 16:22:30 +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-05-09 21:52:53 +02:00

restart_scripts

Do actually stop pki_cad in stop_pkicad instead of starting it.

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

Add ipaRangeType attribute to LDAP Schema

2013-06-10 12:27:33 +03:00

tools

Manage ipa-otpd.socket by IPA

2013-06-06 18:16:59 +02:00

Fix regression: missing facet tab group labels

2013-06-05 14:51:45 +02:00

updates

Add ipaRangeType attribute to LDAP Schema

2013-06-10 12:27:33 +03:00

wsgi

Generate plugin index dynamically

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

configure.ac

Generate plugin index dynamically

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

Makefile.am

Generate plugin index dynamically

2013-05-06 16:22:30 +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.