URL: https://github.com/freeipa/freeipa/pull/5312
Author: rcritten
Title: #5312: Move where the restore state is marked during IPA server upgrade
Action: opened
PR body:
"""
There is still some exposure to killing in a bad place. This was
reproduced by killing the process in the parser.parse() call within
__restore_config (line 230) so the values were restored from the
backup but the new dse.ldif never written or copied. But the values
had already been restored from the state file.
I'm not sure this can ever be 100% bullet-proof since it can be
externally killed but if rather than calling restore_state() on the
values in __restore_config we use get_state() which will peek at the
values in the state file without removing them. Then the last step
is to pop upgrade-in-progress and then the rest.
If the values have been restored and the new ldif written and copied
then it's only upgrade-in-progress that really matters. The rest will
be overwritten.
https://pagure.io/freeipa/issue/7534
Signed-off-by: Rob Crittenden <rcritten(a)redhat.com>
"""
To pull the PR as Git branch:
git remote add ghfreeipa https://github.com/freeipa/freeipa
git fetch ghfreeipa pull/5312/head:pr5312
git checkout pr5312
URL: https://github.com/freeipa/freeipa/pull/5305
Author: rcritten
Title: #5305: Add IPA RA Agent to ACME group on the CA
Action: opened
PR body:
"""
Add IPA RA Agent to ACME group on the CA
Move the addition of the RA agent to the ACME Enterprise Users
group into setup_acme() so it is also added on upgrades.
This allows ipa-acme-manage to authenticate to the CA REST
API using the RA Agent credentials.
https://pagure.io/freeipa/issue/8603
Signed-off-by: Rob Crittenden <rcritten(a)redhat.com>
"""
To pull the PR as Git branch:
git remote add ghfreeipa https://github.com/freeipa/freeipa
git fetch ghfreeipa pull/5305/head:pr5305
git checkout pr5305
URL: https://github.com/freeipa/freeipa/pull/5294
Author: rcritten
Title: #5294: Allow Apache to answer to ipa-ca requests without a redirect
Action: opened
PR body:
"""
Allow Apache to answer to ipa-ca requests without a redirect
Any request other than the FQDN is redirected with a permanent
move (301). Allowing ipa-ca as a valid name saves a round-trip.
This is only allowed on /ca, /kra, /pki, /acme and /ipa/crl.
https://pagure.io/freeipa/issue/8595
Signed-off-by: Rob Crittenden <rcritten(a)redhat.com>
"""
To pull the PR as Git branch:
git remote add ghfreeipa https://github.com/freeipa/freeipa
git fetch ghfreeipa pull/5294/head:pr5294
git checkout pr5294
URL: https://github.com/freeipa/freeipa/pull/5310
Author: flo-renaud
Title: #5310: [Backport][ipa-4-9] Change KRA profiles in certmonger tracking so they can renew
Action: opened
PR body:
"""
This PR was opened automatically because PR #5199 was pushed to master and backport to ipa-4-9 is required.
"""
To pull the PR as Git branch:
git remote add ghfreeipa https://github.com/freeipa/freeipa
git fetch ghfreeipa pull/5310/head:pr5310
git checkout pr5310
URL: https://github.com/freeipa/freeipa/pull/5309
Author: flo-renaud
Title: #5309: [Backport][ipa-4-8] Change KRA profiles in certmonger tracking so they can renew
Action: opened
PR body:
"""
This PR was opened automatically because PR #5199 was pushed to master and backport to ipa-4-8 is required.
"""
To pull the PR as Git branch:
git remote add ghfreeipa https://github.com/freeipa/freeipa
git fetch ghfreeipa pull/5309/head:pr5309
git checkout pr5309
URL: https://github.com/freeipa/freeipa/pull/5199
Author: rcritten
Title: #5199: Change KRA profiles in certmonger tracking so they can renew
Action: opened
PR body:
"""
Change KRA profiles in certmonger tracking so they can renew
Internal profiles were assigned which prevented rewewals.
dogtag is providing a new profile for the audit signing cert,
caAuditSigningCert.
There are existing profiles for the transport (caTransportCert)
and storage (caStorageCert) certificates.
https://pagure.io/freeipa/issue/8545
Signed-off-by: Rob Crittenden <rcritten(a)redhat.com>
**NOTE**: This is WIP because the necessary profile is only in the pki nightly repo. We want this backported to other supported IPA branches but they may be delayed depending on when pki builds are available.
"""
To pull the PR as Git branch:
git remote add ghfreeipa https://github.com/freeipa/freeipa
git fetch ghfreeipa pull/5199/head:pr5199
git checkout pr5199
URL: https://github.com/freeipa/freeipa/pull/5308
Author: flo-renaud
Title: #5308: [Backport][ipa-4-9] Issue 7975 - Accept 389-ds JSON replication status messages
Action: opened
PR body:
"""
This PR was opened automatically because PR #3275 was pushed to master and backport to ipa-4-9 is required.
"""
To pull the PR as Git branch:
git remote add ghfreeipa https://github.com/freeipa/freeipa
git fetch ghfreeipa pull/5308/head:pr5308
git checkout pr5308
URL: https://github.com/freeipa/freeipa/pull/3275
Author: marcus2376
Title: #3275: Issue 7975 - Accept 389-ds JSON replication status messages
Action: opened
PR body:
"""
Description:
389-ds now stores a replication agreement status message in a JSON string in a new attribute:
replicaLastInitStatusJSON
replicaLastUpdateStatusJSON
The original status attributes' values are not changing at this time, but there are plans to do so eventually as the old status format is confusing.
http://www.port389.org/docs/389ds/design/repl-agmt-status-design.htmlhttps://pagure.io/freeipa/issue/7975
Reviewed by: ?
"""
To pull the PR as Git branch:
git remote add ghfreeipa https://github.com/freeipa/freeipa
git fetch ghfreeipa pull/3275/head:pr3275
git checkout pr3275
URL: https://github.com/freeipa/freeipa/pull/5304
Author: flo-renaud
Title: #5304: [Backport][ipa-4-9] Always define the path DNSSEC_OPENSSL_CONF
Action: opened
PR body:
"""
This PR was opened automatically because PR #5292 was pushed to master and backport to ipa-4-9 is required.
"""
To pull the PR as Git branch:
git remote add ghfreeipa https://github.com/freeipa/freeipa
git fetch ghfreeipa pull/5304/head:pr5304
git checkout pr5304