From Fedora Project Wiki

Revision as of 00:54, 9 July 2014 by Adamwill (talk | contribs) (add server acceptance category)

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.


Join the current machine to an Active Directory using Anaconda's kickstart.


  1. Make sure you have the required software:
    • realmd 0.14.0 or later
    • adcli 0.7 or later
    • A non-live installer image for the Fedora release you wish to test
  2. Verify that your Active Directory domain access works, or set a domain up.
  3. Precreate a computer account in the domain with a one time password using adcli:
    $ adcli preset-computer --one-time-password=MyPassword anaconda1
    The computer name above must match the name in the ks.cfg file below.
    Replace your domain name.
  4. Create a new virtual machine with at least an 8GB disk and 1GB of RAM, using the installer image to boot from
  5. Prepare the kickstart file
    Create a file based on the one below, replacing your domain name into the realm command and the correct Fedora version and architecture into the url command (and making any other adjustments as necessary)
    Upload the kickstart file to your account or some other accessible http server (or use another method of kickstart deployment, whatever is most convenient)
bootloader --location=mbr
network --bootproto=dhcp --hostname=anaconda1
url --url
timezone Europe/Prague
lang en_US.UTF-8
clearpart --all
realm join --one-time-password=MyPassword
rootpw anaconda

How to test

  1. Start your new virtual machine you prepared above
  2. At the Fedora boot loader install prompt, use the arrow keys to select Install Fedora 28 and press tab.
  3. Add the following to the end of the command line
    Make sure to use the full path to the location you uploaded your custom ks.cfg file (or adjust as necessary for any other kickstart deployment method).
  4. Press enter to boot and run the installation.

Expected Results

  1. The boot should complete without prompting
    If you watch closely, before install you should see a status line saying that the realm is being discovered
    Again, after installation, you should see a status line joining the domain.
  2. Reboot the machine after installation
  3. Log in as root, using the root password in the ks.cfg
  4. Check if you are joined to the domain
    realm list
    The domain should be listed
    Make note of the login format
  5. Check that domain accounts can be resolved
    getent passwd 'AD\User'
    Make sure to use the quotes around the user name.
    You should see an output line that looks like passwd(5) output. It should contain an appropriate home directory, and a shell.
    Use the login-formats you saw above, to build a remote user name. It will be in the form of DOMAIN\User, where DOMAIN is the first part of your full Active Directory domain name.
  6. Check that you have an appropriate entry in your hosts keytab.
    sudo klist -k
  7. Check that you can use your keytab with kerberos
    sudo kinit -k 'HOSTNAME$@AD.EXAMPLE.COM'
    Make sure to use quotes around the argument, because of the characters in there. #: Make sure the hostname and domain are capitalized.
    Use the principal from the output of the klist command above. Use the one that's capitalized and looks like HOSTNAME$@DOMAIN.
    There should be no output from this command.
  8. Try to log into the machine as a domain account at the console.
    This should automatically create a new home directory for the user, and log into a shell prompt.

More: Try it with FreeIPA

Use a FreeIPA domain with kickstart.

Instead of the adcli preset-computer command, use the FreeIPA Web UI to precreate an account with the appropriate name.


  • If the domain is not resolvable by the DHCP/DNS server used by the virtual machine's virtual switch, you can configure network settings directly in the kickstart file using the "network" keyword. For example:
network --bootproto=static --ip=<vm-static-ip-address> --netmask=<vm-netmask> --gateway=<vm-gateway> --nameserver=<ad-dns-server-ip-address> --hostname=anaconda1
  • If the adcli preset-computer command above complains about the computer account already existing, you can delete it with a command like this:
$ adcli delete-computer anaconda1