From Fedora Project Wiki

(whoops, mispaste)
m (damnit)
Line 22: Line 22:
# If the admin credentials prompt is necessary, it should appear and the join process should start when you enter correct admin credentials and click Continue.
# If the admin credentials prompt is necessary, it should appear and the join process should start when you enter correct admin credentials and click Continue.
# You should be able to log in as the FreeIPA user configured during this test.
# You should be able to log in as the FreeIPA user configured during this test.
# You should be able to run tasks that require access to the FreeIPA domain (to confirm the join and login work correctly).
# You should be able to run tasks that require access to the FreeIPA domain (to confirm the join and login work correctly).}}


[[Category:Realmd_Test_Cases]] [[Category:FreeIPA_Test_Cases]]
[[Category:Realmd_Test_Cases]] [[Category:FreeIPA_Test_Cases]]
[[Category:Server Acceptance Test Cases]]
[[Category:Server Acceptance Test Cases]]

Revision as of 00:57, 9 September 2014

Note.png
Associated release criterion
This test case is associated with the Basic_Release_Criteria#remote-authentication 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

Join the current machine to a FreeIPA domain using GNOME's initial setup tool. Domain accounts are available on the local machine once this is done.

Setup

  1. This test case assumes you have already set up a FreeIPA domain (named "ipa.example.org" in this example - adjust as appropriate for your local configuration). If you haven't, you can set one up. QA:Testcase_freeipav3_installation can function as an instruction set for this purpose; also see the FreeIPA Guide.
  2. Your machine must have a fully-qualified host name. Do not proceed if the output of hostname is localhost or localhost.localdomain or similar. It should be something like test-system.example.org.
  3. Make sure you have realmd-0.13.3-2 or later installed: rpm -q realmd

How to test

  1. Install Fedora Workstation (or, for releases older than Fedora 21, do a standard Fedora GNOME desktop install), using all defaults where possible and sensible settings elsewhere. Do not create a local user account during installation.
  2. Boot the installed system.
  3. On the About You page of the wizard, click Set Up Enterprise Login.
  4. Enter the FreeIPA domain name (for e.g. example.org) for Domain (it should be available as a choice from the drop-down box if your test system's hostname is as suggested above), and a valid username and password for a user account on the domain, and click Next.
  5. If prompted for administrator credentials, enter the username and password of the FreeIPA domain administrator account and click Continue.
  6. Complete the wizard, and try to log in with the user account you configured.
  7. Check whether you can run getent passwd someuser@example.org and other commands that would require correct authentication with the FreeIPA domain.

Expected Results

  1. Installation should run successfully. If it does not, you have made a mistake or encountered a failure of one of the Installer Test Cases.
  2. The GNOME initial setup wizard should appear before any login screen. If it does not, consider this a failure of QA:Testcase_base_initial_setup.
  3. The user creation step should switch to an 'Enterprise Login' mode when you click the Set Up Enterprise Login button.
  4. If the user account you chose to set up has the power to enrol new client systems in the domain, the joining process should start as soon as you enter the account details and click Next. If not, a dialog requesting the credentials of an account with the necessary powers should appear.
  5. If the admin credentials prompt is necessary, it should appear and the join process should start when you enter correct admin credentials and click Continue.
  6. You should be able to log in as the FreeIPA user configured during this test.
  7. You should be able to run tasks that require access to the FreeIPA domain (to confirm the join and login work correctly).