freeipa

0 Fork 0

Files

T

Endi S. Dewata c5ce14c83a Fixed error after login on IE

The IE does not resend the request body during negotiation, so after
after a successful authentication the server could not find the JSON
request to parse.

The Web UI has been modified to detect this error and resend the
initialization request.

Ticket #1540

2011-08-09 14:04:06 +00:00

conf

rename static to ui

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

html

Redirection after changing browser configuration

2011-08-08 13:49:26 -04:00

migration

Removed FreeWay font files.

2011-06-20 12:59:05 -04:00

Make dogtag an optional (and default un-) installed component in a replica.

2011-06-23 19:04:33 -04:00

Redirection after changing browser configuration

2011-08-08 13:49:26 -04:00

tools

Ask for reverse DNS zone information in attended install right after asking for DNS forwarders, so that DNS configuration is done in one place.

2011-08-09 13:12:19 +02:00

Fixed error after login on IE

2011-08-09 14:04:06 +00:00

updates

Correct sudo runasuser and runasgroup attributes in schema

2011-07-19 08:06:41 -04:00

configure.ac

Removed custom layouts using HTML templates.

2011-07-21 11:47:57 -04: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.