From Fedora Project Wiki
m (Stefw moved page QA:Testcase Active Directory realmd login to QA:Testcase realmd login) |
(Update requirements) |
||
Line 2: | Line 2: | ||
|description=Permit a domain account to log in locally, and then test that login. | |description=Permit a domain account to log in locally, and then test that login. | ||
|setup= | |setup= | ||
# If you are linked to your Active Directory domain via VPN, then this Test case will not work. | # If you are linked to your Active Directory domain via VPN, then this Test case will not work. | ||
# [[ | # Make sure you have other required software: | ||
#* realmd 0.14.0 or later | |||
# Verify that your [[QA:Testcase_Active_Directory_Setup|Active Directory domain access works, or set a domain up]]. | |||
# Run through the [[QA:Testcase_Active_Directory_realmd_join_sssd|test case to join the domain]]. | # Run through the [[QA:Testcase_Active_Directory_realmd_join_sssd|test case to join the domain]]. | ||
# Verify that you are joined to the domain with the following command | # Verify that you are joined to the domain with the following command | ||
Line 29: | Line 29: | ||
#: On a Live CD if you get automatically logged in again, go to ''User Accounts'' and turn off Auto Login for the live cd user. | #: On a Live CD if you get automatically logged in again, go to ''User Accounts'' and turn off Auto Login for the live cd user. | ||
# Choose the ''Not Listed?'' option. | # Choose the ''Not Listed?'' option. | ||
# Type <code>DOMAIN\User</code> in the box. | # Type <code>DOMAIN\User</code> in the box. | ||
#: The case of the domain and user should not matter, but they are separated by a backslash. | #: The case of the domain and user should not matter, but they are separated by a backslash. | ||
Line 45: | Line 44: | ||
If the above explodes, try to log in from a VT console, and see if there is any interesting output there. | If the above explodes, try to log in from a VT console, and see if there is any interesting output there. | ||
If you are connected to your domain controller via VPN, the above test case will not work. | If you are connected to your domain controller via VPN, the above test case will not work. | ||
[[Category:Active_Directory_Test_Cases]] [[Category:Realmd_Test_Cases]] | [[Category:Active_Directory_Test_Cases]] [[Category:Realmd_Test_Cases]] |
Revision as of 06:34, 9 May 2013
Description
Permit a domain account to log in locally, and then test that login.
Setup
- If you are linked to your Active Directory domain via VPN, then this Test case will not work.
- Make sure you have other required software:
- realmd 0.14.0 or later
- Verify that your Active Directory domain access works, or set a domain up.
- Run through the test case to join the domain.
- Verify that you are joined to the domain with the following command
$ realm list
- Make sure you have a
configured: kerberos-membership
line in the output. - Note the
login-formats:
line.
- Check that you can resolve domain accounts on the local computer.
- Use the
login-formats
you saw above, to build a remote user name. It will be in the form ofDOMAIN\User
, where DOMAIN is the first part of your full Active Directory domain name. $ getent passwd 'AD\User'
- Use the
How to test
- Perform the permit command.
$ realm permit --realm=ad.example.com 'AD\User'
- You will be prompted for Policy Kit authorization.
- You will not be prompted for a password.
- This should proceed quickly, not take more that 10 seconds.
- On a successful permit there will be no output.
- The user should show up here:
$ realm list
- Look at the
permitted-logins:
line. - You should also see
login-policy: allow-permitted-logins
.
- Go to GDM by logging out, or by Switch User from the user menu.
- On a Live CD if you get automatically logged in again, go to User Accounts and turn off Auto Login for the live cd user.
- Choose the Not Listed? option.
- Type
DOMAIN\User
in the box.- The case of the domain and user should not matter, but they are separated by a backslash.
- The domain part is the part of your Active Directory domain prior to the first dot.
- Type the user domain password, and press enter.
Expected Results
- You should be logged into the Fedora desktop.
- Open a terminal, and type:
$ id
- Look at the output to verify that you are logged in as a domain user.
Troubleshooting
If the above explodes, try to log in from a VT console, and see if there is any interesting output there.
If you are connected to your domain controller via VPN, the above test case will not work.