freeipa

mirror of https://salsa.debian.org/freeipa-team/freeipa.git synced 2024-12-26 17:01:14 -06:00

History

Petr Vobornik 8d892f442f Better error message for login of users from other realms When user from other realm than FreeIPA's tries to use Web UI (login via forms-based auth or with valid trusted realm ticket), he gets an unauthorized error with X-Ipa-Rejection-Reason=denied. Web UI responds with showing login dialog with following error message: 'Sorry you are not allowed to access this service.'. Note: such users are not supported because they don't have a corresponding entry in LDAP which is needed for ACLs. https://fedorahosted.org/freeipa/ticket/3252 denied change		2012-12-06 17:02:03 +01:00
..
certmonger	Use DN objects instead of strings	2012-08-12 16:23:24 -04:00
conf	Configure the initial CA as the CRL generator.	2012-10-09 19:24:43 -04:00
ffextension	Kerberos authentication extension makefiles	2012-10-04 18:07:34 -04:00
html	Removal of delegation-uris instruction from browser config	2012-10-04 18:35:47 -04:00
migration	Use DN objects instead of strings	2012-08-12 16:23:24 -04:00
po	Pull translation files from Transifex	2012-10-11 16:09:27 -04:00
restart_scripts	Wait for the directory server to come up when updating the agent certificate.	2012-11-01 13:36:52 -04:00
share	Specify includedir in krb5.conf on new installs	2012-12-06 10:53:22 -05:00
tools	Improve ipa-replica-prepare error message	2012-12-06 08:00:27 +01:00
ui	Better error message for login of users from other realms	2012-12-06 17:02:03 +01:00
updates	Enable transactions by default, make password and modrdn TXN-aware	2012-11-21 14:55:12 +01:00
configure.ac	Kerberos authentication extension makefiles	2012-10-04 18:07:34 -04:00
Makefile.am	Move CRL publish directory to IPA owned directory	2012-10-09 16:00:01 +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.