freeipa

0 Fork 0

Files

T

Petr Vobornik 905d58a2a4 webui: handle back button when unauthenticated

using browser history when unauthenticated causes transition to
the original and/or preceding facets. But nothing works since
all commands fail due to expired credentials in session.

These changes make sure that user stays on login screen if he misses
valid session credentials while he wants to switch to facet which
requires authentication.

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

Reviewed-By: Endi Sukma Dewata <edewata@redhat.com>

2014-06-11 13:54:20 +02:00

certmonger

Support exporting CSRs in dogtag-ipa-ca-renew-agent.

2014-03-25 16:54:56 +01:00

conf

Use certmonger D-Bus API to configure certmonger in CA install.

2014-03-25 16:54:54 +01:00

ffextension

Kerberos authentication extension makefiles

2012-10-04 18:07:34 -04:00

html

webui: remove remnants of jquery-ui

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

migration

webui: remove remnants of jquery-ui

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

fix typo in ipa -v migrate-ds

2014-03-21 13:08:03 +01:00

restart_scripts

Merge restart_httpd functionality to renew_ra_cert.

2014-03-25 16:54:55 +01:00

Convert User default permissions to managed

2014-06-10 13:55:56 +02:00

tools

admin tools: Log IPA version

2014-05-27 12:08:55 +02:00

webui: handle back button when unauthenticated

2014-06-11 13:54:20 +02:00

updates

Convert User default permissions to managed

2014-06-10 13:55:56 +02:00

wsgi

Generate plugin index dynamically

2013-05-06 16:22:30 +02:00

configure.ac

RCUE initial commit

2014-01-21 12:04:02 +01: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.