freeipa

0 Fork 0

Files

T

Rob Crittenden 8719336652 Allow a client to enroll using principal when the host has a OTP

If the host has a one-time password but krbPrincipalName wasn't set yet
then the enrollment would fail because writing the principal is not
allowed. This creates an ACI that only lets it be written if it is not
already set.

ticket 1075

2011-03-30 10:03:44 -04:00

conf

rename static to ui

2011-01-20 14:12:47 +00:00

html

error handling style

2011-01-25 16:47:09 -05:00

migration

Use ldapi: instead of unsecured ldap: in ipa core tools.

2011-03-03 14:04:34 -05:00

Update translation file (ipa.pot).

2011-03-18 14:59:34 -04:00

Store list of non-master replicas in DIT and provide way to list them

2011-03-02 09:46:46 -05:00

tools

Replica installation fails for self-signed server

2011-03-30 10:00:13 -04:00

Fixed undefined label in permission adder dialog box.

2011-03-29 17:52:19 -04:00

updates

Allow a client to enroll using principal when the host has a OTP

2011-03-30 10:03:44 -04:00

configure.ac

rename static to ui

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