freeipa

0 Fork 0

Files

T

Petr Vobornik cd5fe9b407 webui: don't log in back after logout

Automatic login attempt is initiated by first failed xhr request which
happens in metadata phase.

New phase was added before metadata phase. It interrupts UI load and shows
login page if it's directly after logout(marked in session storage).
Successfull manual login resolves the phase so that metadata phase can
follow.

https://fedorahosted.org/freeipa/ticket/5008

Reviewed-By: Martin Basti <mbasti@redhat.com>

2015-06-05 19:16:49 +02:00

certmonger

Adopted kinit_keytab and kinit_password for kerberos auth

2015-04-20 08:27:35 +00:00

conf

ipa-pki-proxy: allow certificate and password authentication

2015-06-05 19:12:46 +02:00

ffextension

webui: append network.negotiate-auth.trusted-uris

2014-09-11 09:41:51 +02:00

html

webui: remove remnants of jquery-ui

2014-06-10 10:23:22 +02:00

migration

ipaplatform: Move all filesystem paths to ipaplatform.paths module

2014-06-16 19:48:20 +02:00

Add a KRA to IPA

2014-08-22 09:59:31 +02:00

restart_scripts

Adopted kinit_keytab and kinit_password for kerberos auth

2015-04-20 08:27:35 +00:00

Add usercertificate attribute to user plugin

2015-06-04 08:27:33 +00:00

tools

Import included profiles during install or upgrade

2015-06-04 08:27:33 +00:00

webui: don't log in back after logout

2015-06-05 19:16:49 +02:00

updates

Add usercertificate attribute to user plugin

2015-06-04 08:27:33 +00:00

wsgi

Remove trivial path constants from modules

2014-11-04 12:57:01 +01:00

configure.ac

Import included profiles during install or upgrade

2015-06-04 08:27:33 +00:00

Makefile.am

Change group ownership of CRL publish directory

2013-07-16 12:17:40 +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.