freeipa/install
Alexander Bokovoy 03cdc22c94 Resolve SIDs in Web UI
Introduce new command, 'trust-resolve', to aid resolving SIDs to names
in the Web UI.

The command uses new SSSD interface, nss_idmap, to resolve actual SIDs.
SSSD caches resolved data so that future requests to resolve same SIDs
are returned from a memory cache.

Web UI code is using Dojo/Deferred to deliver result of SID resolution
out of band. Once resolved names are available, they replace SID values.

Since Web UI only shows ~20 records per page, up to 20 SIDs are resolved
at the same time. They all sent within the single request to the server.

https://fedorahosted.org/freeipa/ticket/3302
2013-05-06 20:44:00 +02: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 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
po Update translations from Transifex 2013-04-15 18:46:27 +02:00
restart_scripts Do actually stop pki_cad in stop_pkicad instead of starting it. 2013-04-09 16:22:23 +02:00
share Fix syntax errors in schema files 2013-04-26 11:15:16 -04:00
tools Generate plugin index dynamically 2013-05-06 16:22:30 +02:00
ui Resolve SIDs in Web UI 2013-05-06 20:44:00 +02:00
updates Fix syntax errors in schema files 2013-04-26 11:15:16 -04: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

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.