From Fedora Project Wiki
 
Line 107: Line 107:


Visit the '''[http://testdays.fedoraproject.org/events/191 results page]''' and click on the column title links to see the tests that need to be run: most column titles are links to a specific test case. Follow the instructions there, then enter your results by clicking the ''Enter result'' button for the test.
Visit the '''[http://testdays.fedoraproject.org/events/191 results page]''' and click on the column title links to see the tests that need to be run: most column titles are links to a specific test case. Follow the instructions there, then enter your results by clicking the ''Enter result'' button for the test.
Test results will be exported here once the test day is over. See [[#How_to_test?|How to test?]] section for information how to submit results and see the live results.
 
=== Basic ===
{| class="wikitable" width=100%
! User
! Profile
! [http://fedoraproject.org/wiki/QA:Testcase_basicIPA_with_HSM basicIPAwithHSM]
! [http://fedoraproject.org/wiki/QA:Testcase_IPA_server_replica_HSM IPA server with replica HSM]
! References
|-
| [[User:felipetg|felipetg]]
| VM using Fedora Rawhide (latest iso available)
| {{result|fail}}<ref>Issue 9623 created</ref>
|
| <references/>
|-
| [[User:sumenon|sumenon]]
|
| {{result|pass}}{{result|pass}}<ref>Ignore https://pagure.io/freeipa/issue/9622</ref>{{result|fail}}<ref>https://pagure.io/freeipa/issue/9622</ref>
| {{result|pass}}
| <references/>
 
|-
|}
 
=== Key Recovery Authority (KRA) ===
{| class="wikitable" width=100%
! User
! Profile
! [http://fedoraproject.org/wiki/QA:Testcase_Install_IPA_with_KRA IPA with KRA]
! [http://fedoraproject.org/wiki/QA:Testcase_Install_IPA_Server_replica_with_KRA IPA Server replica with KRA]
! References
|-
| [[User:sumenon|sumenon]]
| Fedora41
| {{result|pass}}<ref>KRA install is successful with the --token-password and --token-name option.
ipatoken: storageCert(u,u,u), auditSigningCert(u,u,Pu), transportCert(u,u,u), subsystemCert(u,u,u) are listed using 'certutil -L -d /etc/pki/pki-tomcat/alias -h ipa_token'
Vault can be added, data can be archived and retrieved.
</ref>
| {{result|pass}}<ref>Installation of Replica prompts 'Enter Password or Pin for "ipa_token":
The TOKEN_PASSWORD is already specified in the command.
https://pagure.io/freeipa/issue/9603</ref>
| <references/>
 
|-
|}
 
=== Certificate Reissue ===
{| class="wikitable" width=100%
! User
! Profile
! [http://fedoraproject.org/wiki/QA:Testcase_Install_IPA_HSM_renew_cert Outisde grace period]
! [http://fedoraproject.org/wiki/QA:Testcase_Install_IPA_HSM_renew_cert_within_grace Within grace period]
! References
|-
| [[User:sumenon|sumenon]]
| Fedora41
| {{result|pass}}<ref>IPA certs expire in 2years
Current Date: Thu Jul 11 02:44:31 PM IST 2024
Cert Expires: 2026-07-01 14:32:04 IST
Modified Time: date -s +1years+11months+20days, Wed Jul  1 02:45:06 PM IST 2026
root@server:~# ipa-cert-fix
Becoming renewal master.
Restarting IPA
The ipa-cert-fix command was successful
getcert list | grep status -- the certificates go through different states  and finally in MONITORING state.
Certificates (excluding the CA cert) are re-issued correctly when expired.
</ref>
| {{result|pass}}<ref>ALL Certs are VALID and in MONTORING State after certmonger renews them.</ref>{{result|pass}}<ref>For this test the system date is to be moved within 30 days of expiration to test that certmonger would renew things.
Seeing ca-error: Server at "http://server.fedora41.test:8080/ca/ee/ca/profileSubmit" replied: access denied ("java.io.FilePermission" "/var/lib/pki/pki-tomcat/logs/ca" "read") which is known issue for pki.
Current Date: Wed Jul 10 07:13:59 PM IST 2024
Certs Expire: 2026-06-30 12:02:08 IST
Modified Date: date -s 'Wed Jun 07 06:54:58 PM IST 2026'
Restart ipactl.
 
 
 
 
 
</ref>
| <references/>
 
|-
|}
 
 






[[Category:Fedora 41 Test Days]]
[[Category:Fedora 41 Test Days]]

Latest revision as of 05:44, 14 July 2024


IPA HSM Test DAy
Date 2024-07-09 to 2024-07-11
Time all day
Website QA/Test Days
Matrix #test-day:fedoraproject.org(other clients|?)
Mailing list test


Can't make the date?
If you come to this page after the test day is completed, your testing is still valuable, and you can use the information on this page to test, file any bugs you find, and add your results to the results section. If this page is more than a month old when you arrive here, please check the current schedule and see if a similar but more recent Test Day is planned or has already happened.

What to test?[edit]

This Test Day will focus on FreeIPA HSM

Who's available[edit]

The following cast of characters will be available testing, workarounds, bug fixes, and general discussion:

You can chat with me on Matrix. See the infobox on top of the page to learn where to join.

Prerequisite for Test Day[edit]

  • A virtual machine or a bare metal machine
  • An installation of Fedora 40 (ideally Server). Make sure to fully update your system. If installing a fresh system, it's recommended to use the latest nightly image.

What to test[edit]

This will focus on testing IPA support for generating and storing CA private keys on a Hardware Security Module (HSM).

There are two supported HSMs: the nCipher nShield Connect XC (High) and the Thales TCT Luna Network HSM Luna-T7. Firmware versions can vary so only specific ones are supported.

Using softhsm2 as an HSM is usable for testing. It is not recommended for production because it is not a truly networked HSM and the private keys live on a file system (protected yes but not at a hardware level). Because it is not networked, users will need to carefully synchronize the token files whenever any private key generation is done to ensure the contents are identical.

How to test?[edit]

Install freeIPA packages[edit]

  1. dnf -y install freeipa-server-dns

Pre-configure the HSM[edit]

If you are using softhsm2, grant read access to the tokens: 

 # usermod pkiuser -a -G ods

Set up environment variables on each machine/VM[edit]

 # export TOKEN_PASSWORD=password
 # export ADMIN_PASSWORD=password
 # export DM_PASSWORD=password

If using a supported hardware HSM ensure that it is working properly and have the token name and PKCS#11 library path handy.

In between tests[edit]

To re-use test machines in between installations:

On replica (if there is one) 

 # ipa server-del $HOSTNAME
 # ipa-server-install –uninstall -U

On the initial IPA server 

 # ipa-server-install –uninstall -U

If using softhsm2 you will also need to delete and re-create the token. To delete the token: 

 # softhsm2-util --delete-token --token ipa_token

This should return the machine(s) to the pre-installed state.

Visit the results page and click on the column title links to see the tests that need to be run: most column titles are links to a specific test case. Follow the instructions there, then enter your results by clicking the Enter result button for the test.

Reporting bugs[edit]

Perhaps you've found an already-reported bug. Please look at:

All new bugs should be reported into the upstream bug tracker. A less-preferred alternative is to file them into Red Hat JIRA, in most cases against the ipa component.

We really need bug reports!
Please note that just mentioning your problem into the comments section on the results page is not very helpful. Very often those problems only happen in specific circumstances, or with specific steps taken. We need the logs and screenshots, and we need to be able to ask you followup questions. Please file bug reports, it's much more useful than a short comment. Thank you!

When filing the bug, it's very helpful to include:

  • exact steps you've performed (and whether you can reproduce it again)
  • screenshots or videos, if applicable
  • system journal (log), which you can retrieve by journalctl -b > journal.txt
  • all output in a terminal, if started from a terminal
  • your system description

If you are unsure about exactly how to file the report or what other information to include, just ask us.

Please make sure to link to the bug when submitting your test result, thanks!

Test Results[edit]

Visit the results page and click on the column title links to see the tests that need to be run: most column titles are links to a specific test case. Follow the instructions there, then enter your results by clicking the Enter result button for the test.

Basic[edit]

User Profile basicIPAwithHSM IPA server with replica HSM References
felipetg VM using Fedora Rawhide (latest iso available)
Fail fail
[1]
  1. ↑ Issue 9623 created
sumenon
Pass pass
Pass pass
[1]
Fail fail
[2]
Pass pass
  1. ↑ Ignore https://pagure.io/freeipa/issue/9622
  2. ↑ https://pagure.io/freeipa/issue/9622

Key Recovery Authority (KRA)[edit]

User Profile IPA with KRA IPA Server replica with KRA References
sumenon Fedora41
Pass pass
[1]
Pass pass
[2]
  1. ↑ KRA install is successful with the --token-password and --token-name option. ipatoken: storageCert(u,u,u), auditSigningCert(u,u,Pu), transportCert(u,u,u), subsystemCert(u,u,u) are listed using 'certutil -L -d /etc/pki/pki-tomcat/alias -h ipa_token' Vault can be added, data can be archived and retrieved.
  2. ↑ Installation of Replica prompts 'Enter Password or Pin for "ipa_token": The TOKEN_PASSWORD is already specified in the command. https://pagure.io/freeipa/issue/9603

Certificate Reissue[edit]

User Profile Outisde grace period Within grace period References
sumenon Fedora41
Pass pass
[1]
Pass pass
[2]
Pass pass
[3]
  1. ↑ IPA certs expire in 2years Current Date: Thu Jul 11 02:44:31 PM IST 2024 Cert Expires: 2026-07-01 14:32:04 IST Modified Time: date -s +1years+11months+20days, Wed Jul 1 02:45:06 PM IST 2026 root@server:~# ipa-cert-fix Becoming renewal master. Restarting IPA The ipa-cert-fix command was successful getcert list | grep status -- the certificates go through different states and finally in MONITORING state. Certificates (excluding the CA cert) are re-issued correctly when expired.
  2. ↑ ALL Certs are VALID and in MONTORING State after certmonger renews them.
  3. ↑ For this test the system date is to be moved within 30 days of expiration to test that certmonger would renew things. Seeing ca-error: Server at "http://server.fedora41.test:8080/ca/ee/ca/profileSubmit" replied: access denied ("java.io.FilePermission" "/var/lib/pki/pki-tomcat/logs/ca" "read") which is known issue for pki. Current Date: Wed Jul 10 07:13:59 PM IST 2024 Certs Expire: 2026-06-30 12:02:08 IST Modified Date: date -s 'Wed Jun 07 06:54:58 PM IST 2026' Restart ipactl.
Retrieved from "https://fedoraproject.org/w/index.php?title=Test_Day:Test_Day:2024-07-09_IPA_HSM&oldid=714427"