March 2021 - FreeIPA-devel - Fedora Mailing-Lists

[freeipa PR#5669][opened] Adapt redhat ipaplatform to RHEL9/ELN

by flo-renaud

URL: https://github.com/freeipa/freeipa/pull/5669 Author: flo-renaud Title: #5669: Adapt redhat ipaplatform to RHEL9/ELN Action: opened PR body: """ On RHEL8, ipa is using named-pkcs11.service but RHEL9 is based on fedora34 and uses named.service instead. There is already some support for this distinction in ipaplatform, and the patch relies on the specific settings that can be configured in ipaplatform/xx/services.py and ipaplatform/xx/constants.py On RHEL9 ipa also needs to define NAMED_OPENSSL_ENGINE for named to use openssl's okcs11 engine. Fixes: https://pagure.io/freeipa/issue/8753 """ To pull the PR as Git branch: git remote add ghfreeipa https://github.com/freeipa/freeipa git fetch ghfreeipa pull/5669/head:pr5669 git checkout pr5669

3 years

2
1
0 / 0

[freeipa PR#5667][opened] [Backport][ipa-4-9] Don't start the CA during healthcheck grace period check so uninstall succeeds

by rcritten

URL: https://github.com/freeipa/freeipa/pull/5667 Author: rcritten Title: #5667: [Backport][ipa-4-9] Don't start the CA during healthcheck grace period check so uninstall succeeds Action: opened PR body: """ This PR was opened manually because PR #5573 was pushed to master and backport to ipa-4-9 is required. A manual backport was needed because there was a merge conflict in updating the test_integration/test_ipahealthcheck.py::TestIpaHealthCheck timeouts Adding needs_review to double-check I did the merge correctly. """ To pull the PR as Git branch: git remote add ghfreeipa https://github.com/freeipa/freeipa git fetch ghfreeipa pull/5667/head:pr5667 git checkout pr5667

3 years, 1 month

2
1
0 / 0

[freeipa PR#5666][opened] [Backport][ipa-4-8] ipatests: Don't rely on certmonger's assigned request id

by flo-renaud

URL: https://github.com/freeipa/freeipa/pull/5666 Author: flo-renaud Title: #5666: [Backport][ipa-4-8] ipatests: Don't rely on certmonger's assigned request id Action: opened PR body: """ This PR was opened automatically because PR #5659 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/5666/head:pr5666 git checkout pr5666

3 years, 1 month

1
1
0 / 0

[freeipa PR#5665][opened] [Backport][ipa-4-9] ipatests: Don't rely on certmonger's assigned request id

by flo-renaud

URL: https://github.com/freeipa/freeipa/pull/5665 Author: flo-renaud Title: #5665: [Backport][ipa-4-9] ipatests: Don't rely on certmonger's assigned request id Action: opened PR body: """ This PR was opened automatically because PR #5659 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/5665/head:pr5665 git checkout pr5665

3 years, 1 month

1
1
0 / 0

[freeipa PR#5664][opened] [Backport][ipa-4-9] Handle multiple AJP adapters during upgrade

by flo-renaud

URL: https://github.com/freeipa/freeipa/pull/5664 Author: flo-renaud Title: #5664: [Backport][ipa-4-9] Handle multiple AJP adapters during upgrade Action: opened PR body: """ This PR was opened automatically because PR #5256 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/5664/head:pr5664 git checkout pr5664

3 years, 1 month

1
1
0 / 0

[freeipa PR#5573][opened] WIP: Exercise the healthcheck tests to check for DBusError

by rcritten

URL: https://github.com/freeipa/freeipa/pull/5573 Author: rcritten Title: #5573: WIP: Exercise the healthcheck tests to check for DBusError Action: opened PR body: """ We saw the DBusError.NoReply failure in a downstream test. Exercise it a bit. """ To pull the PR as Git branch: git remote add ghfreeipa https://github.com/freeipa/freeipa git fetch ghfreeipa pull/5573/head:pr5573 git checkout pr5573

3 years, 1 month

2
3
0 / 0

[freeipa PR#5659][opened] ipatests: Don't rely on certmonger to assign request id

by mrizwan93

URL: https://github.com/freeipa/freeipa/pull/5659 Author: mrizwan93 Title: #5659: ipatests: Don't rely on certmonger to assign request id Action: opened PR body: """ There are failure observed in test_rekey_keytype_DSA(test_cert.py) It is due to the fact that there is no guarantee that the request id will match the filename that certmonger assigns. So just don't rely on certmonger and specify own request id on commandline. fixes: https://pagure.io/freeipa/issue/8725 Signed-off-by: Mohammad Rizwan <myusuf(a)redhat.com> """ To pull the PR as Git branch: git remote add ghfreeipa https://github.com/freeipa/freeipa git fetch ghfreeipa pull/5659/head:pr5659 git checkout pr5659

3 years, 1 month

2
1
0 / 0

[freeipa PR#5256][opened] Handle multiple AJP adapters during upgrade

by cipherboy

URL: https://github.com/freeipa/freeipa/pull/5256 Author: cipherboy Title: #5256: Handle multiple AJP adapters during upgrade Action: opened PR body: """ In this patch, we ensure we upgrade all AJP adapters with the same secret value if any are missing. This ensures that both IPv4 and IPv6 adapters have the same secret value, so whichever httpd connects to will be in sync. This is consistent with what Dogtag does when provisioning them. Notably missing from this patch is handling of multiple unrelated AJP adapters. In an IPA scenario (and default PKI scenario) this shouldn't be necessary. However, with external load balancing, this might happen. This patch benefits IPA in the scenario when: 1. `pkispawn` runs on an older PKI version (pre-AJP secret, so ~8.2?) 2. pki gets upgraded to 10.10.1 before IPA can provision a secret, resulting in split IPv4/IPv6 adapters -- this would only happen on a direct migration from 8.2 -> 8.4 3. ipa upgrade script then runs to provision an AJP secret value for use with both Dogtag and IPA. Without this patch, only the first (IPv4) adapter would have a secret value provisioned in the above scenario. `Signed-off-by: Alexander Scheel <ascheel(a)redhat.com>` --- Is this scenario likely? Or will IPA have provisioned a secret anyway on older PKI versions? I do not know. """ To pull the PR as Git branch: git remote add ghfreeipa https://github.com/freeipa/freeipa git fetch ghfreeipa pull/5256/head:pr5256 git checkout pr5256

3 years, 1 month

2
1
0 / 0

[freeipa PR#5663][opened] [ipa-4-8] ipatests: remove test cases for unsupported NTLM authentication scenarios

by wladich

URL: https://github.com/freeipa/freeipa/pull/5663 Author: wladich Title: #5663: [ipa-4-8] ipatests: remove test cases for unsupported NTLM authentication scenarios Action: opened PR body: """ """ To pull the PR as Git branch: git remote add ghfreeipa https://github.com/freeipa/freeipa git fetch ghfreeipa pull/5663/head:pr5663 git checkout pr5663

3 years, 1 month

2
1
0 / 0

[freeipa PR#5661][opened] [Backport][ipa-4-9] ipatests: Enable certbot test on rhel

by flo-renaud

URL: https://github.com/freeipa/freeipa/pull/5661 Author: flo-renaud Title: #5661: [Backport][ipa-4-9] ipatests: Enable certbot test on rhel Action: opened PR body: """ This PR was opened automatically because PR #5562 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/5661/head:pr5661 git checkout pr5661

3 years, 1 month

1
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

FreeIPA-devel March 2021