From Fedora Project Wiki

(use domain server setup template)
mNo edit summary
Line 5: Line 5:
|setup=
|setup=
{{Domain server setup}}
{{Domain server setup}}
# Follow [[QA:Testcase_Server_cockpit_default]] to deploy Fedora Server and ensure Cockpit is enabled and accessible
# Follow [[QA:Testcase_Server_cockpit_default]] to deploy Fedora Server on the test client and ensure Cockpit is enabled and accessible
|actions=
|actions=
# Log in to Cockpit with the root account or an administrative user account, and select the system from the host list
# Log in to Cockpit with the root account or an administrative user account, and select the system from the host list

Revision as of 01:51, 25 November 2014

Associated release criterion
This test case is associated with the Fedora_42_Beta_Release_Criteria#cockpit-management-interface release criterion. If you are doing release validation testing, a failure of this test case may be a breach of that release criterion. If so, please file a bug and nominate it as blocking the appropriate milestone, using the blocker bug nomination page.


Description

This test case checks that a system can be enrolled in a FreeIPA or Active Directory domain ('realm') using Cockpit.

Setup

  1. Deploy a correctly-configured FreeIPA or Active Directory domain controller. You can follow:
    QA:Testcase_Server_role_deploy with the Domain Controller role to deploy a FreeIPA domain controller on Fedora 28 or earlier
    QA:Testcase_freeipa_trust_server_installation to deploy a FreeIPA domain controller on Fedora 29 or later
    QA:Testcase_Active_Directory_Setup to deploy an Active Directory domain controller
  2. Follow QA:Testcase_Server_cockpit_default to deploy Fedora Server on the test client and ensure Cockpit is enabled and accessible

How to test

  1. Log in to Cockpit with the root account or an administrative user account, and select the system from the host list
  2. Select System Information
  3. Click Join Domain
  4. Enter correct configuration and credentials for the domain
  5. Test the domain configuration - for instance, run realm list and ensure it is listed, and/or log in to the system as a user configured in the domain

Expected Results

  1. Enrolment must succeed and the system should work as a domain member would be expected to.