freeipa

0 Fork 0

Files

T

Fraser Tweedale b720aa94e9 Update lightweight CA serial after renewal

For CA replicas to pick up renewed lightweight CA signing
certificates, the authoritySerial attribute can be updated with the
new serial number.

Update the renew_ca_cert script, which is executed by Certmonger
after writing a renewed CA certificate to the NSSDB, to update the
authoritySerial attribute if the certificate belongs to a
lightweight CA.

Part of: https://fedorahosted.org/freeipa/ticket/4559

Reviewed-By: Jan Cholasta <jcholast@redhat.com>

2016-06-29 08:52:29 +02:00

certmonger

Load server plugins in certmonger renewal helper

2016-06-08 15:01:07 +02:00

conf

mod_auth_gssapi: enable unique credential caches names

2016-06-24 16:06:49 +02:00

ffextension

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

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

html

Added warning to user for Internet Explorer

2016-04-28 14:28:11 +02:00

migration

Remove unused imports

2015-12-23 07:59:22 +01:00

oddjob

adtrust: support UPNs for trusted domain users

2016-06-11 17:25:50 +02:00

Updated IPA translations

2016-06-21 12:48:17 +02:00

restart_scripts

Update lightweight CA serial after renewal

2016-06-29 08:52:29 +02:00

DNS Locations: cleanup of bininstance

2016-06-28 15:23:51 +02:00

tools

DNS Locations: hide option --no-msdcs in adtrust-install

2016-06-27 13:35:00 +02:00

DNS Servers: Web UI part

2016-06-21 16:53:25 +02:00

updates

Add missing nsSystemIndex attributes

2016-06-27 10:49:51 +02:00

wsgi

Modernize 'except' clauses

2015-08-12 18:17:23 +02:00

configure.ac

CONFIGURE: Replace obsolete macros

2016-03-08 20:02:27 +01:00

Makefile.am

trusts: add support for one-way trust and switch to it by default

2015-07-08 01:56:52 +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.