freeipa

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

Files

Endi S. Dewata 6af5755de5 Fixed "enroll" labels.

Labels using the word "enroll" (except for host enrollment) have
been modified to use more relevant words.

The IPA.add_dialog has been renamed into IPA.entity_adder_dialog
for clarity.

Ticket #1642

2011-10-27 13:47:45 +00:00

conf

Revert "Always require SSL in the Kerberos authorization block."

2011-09-27 08:54:42 +02:00

html

Removed HBAC deny rule warning.

2011-10-26 12:53:28 +00:00

migration

Fixed: Duplicate CSS definitions

2011-10-19 10:44:44 -02:00

Ticket 1718 - Fix Spanish po translation file

2011-10-11 22:46:02 -04:00

Fix nis netgroup config entry so users appear in netgroup triple.

2011-10-27 09:55:58 +02:00

tools

Fix ipa-managed-entries password option long form

2011-10-26 08:55:09 +02:00

Fixed "enroll" labels.

2011-10-27 13:47:45 +00:00

updates

Fix nis netgroup config entry so users appear in netgroup triple.

2011-10-27 09:55:58 +02:00

configure.ac

ticket 1650 - compute accurate translation statistics

2011-08-18 14:25:58 +02:00

Makefile.am

rename static to ui

2011-01-20 14:12:47 +00: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.