QA:Testcase FreeIPA realmd login

From FedoraProject

Jump to: navigation, search
Note.png
Associated release criterion
This test case is associated with the Fedora_22_Beta_Release_Criteria#domain-access-control 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.


Contents

Description

This test case checks that a system enrolled in a FreeIPA domain honors the domain controller's host-based access control (HBAC) rules.

Setup

  1. Deploy a correctly-configured FreeIPA domain controller. You can follow:
    QA:Testcase_Server_role_deploy with the Domain Controller role to deploy a FreeIPA domain controller on Fedora 21 or later
    QA:Testcase_freeipav3_installation to deploy a FreeIPA domain controller on Fedora 20 or earlier
  2. Enrol a test system in the domain. There are various ways to do this. You will find several test cases you can follow in the Server release validation test cases, FreeIPA test cases, and Realmd test cases
  3. The intent here is to set up an HBAC rule which specifies that all access is prohibited, unless it is initiated by a specific user ("testuser")
  4. Make sure you have freeipa-admintools installed
    # yum install freeipa-admintools
  5. Create a FreeIPA user (after acquiring admin credentials)
    $ kinit admin
    $ ipa user-add testuser --first test --last user --password
  6. Create an HBAC rule that allows access to the user you just created
    $ ipa hbacrule-add testrule --servicecat=all --hostcat=all
    $ ipa hbacrule-add-user testrule --users=testuser
  7. Disable the default rule that allows access to everyone
    $ ipa hbacrule-disable allow_all
  8. On the system that joined the domain, change the testuser password for the first time.
    $ kinit testuser@IPA.EXAMPLE.ORG
    You will be prompted to enter a new password here

How to test

  1. On the system that joined the domain, switch to another VT (press Ctrl-Alt-F4).
  2. Try to log in as the admin user.
    host login: admin@ipa.example.org
  3. Now try to log in as test user.
    host login: testuser@ipa.example.org

Expected Results

  1. Log in as the admin user must fail, and log in as the test user must succeed.



More testing - offline logins

  1. Before the test, make sure that credential caching is enabled on the client
    open /etc/sssd/sssd.conf in your editor of choice
    Make sure that cache_credentials=True is present in the [domain] section of sssd.conf
    Restart the SSSD if you modified the config file: service sssd restart
  2. Perform one more login online to cache the credentials
    Disconnect the client from the network. As root, shut down the NM service:
    # service NetworkManager stop
    Log in as the test user again. The login should succeed.
    Don't forget to start the networking again to make sure you're able to run the cleanup

Clean-up after the test

Enable the allow_all rule again to avoid interference with other tests:

$ kinit admin
$ ipa hbacrule-enable allow_all