RH199 LDAP Lab not working
Hi,
In section 3: the "Practice: Connecting to a Central LDAP and Kerberos Server" lab is not working in RH199.
In particular, the part where you type getent passwd ldapuserX returns nothing and the ssh ldapuserX@localhost - the password doesn't work as I get a permission denied error.
Responses
Red Hat
Pro
650 points
Darren,
I'd suggest opening a support case at https://access.redhat.com to get a Red Hat Training Technical Support Engineer to look at your lab. Remember when opening the case to set the Product to "Red Hat Online Learning", that will make sure that your case is routed to a training specialist who has access to your lab environment.
If I recall this exercise correctly, you have to pull down the keytab file from classroom.example.com with wget. If I have that right, I'd check the contents of your keytab file. I've seen many times where students use the wrong case O (It's capital) for the output file and what ends up being in the resulting .keytab is an error message about using the wrong option instead of the actual keytab file.
Not accessing your lab specifically, that's just a guess based off my previous experiences, a TSE should be able to diagnose this more specifically than a vague gut feeling...
-STM
Red Hat
Pro
650 points
Being the author of the exercise, I’m fairly confident that it works ;-) Also, I’ve not seen consistent reports to the contrary. But, again, I think support are the best folks to help.
Red Hat Online Training does provide a support entitlement with its purchase. It’s possible that the support assignment was misassigned or, if you’re using a corporate user login, that your organization administrator has set your account to not have permission to open cases. For this issue, I’d start with the training operations folks for your geography: https://rol.redhat.com/rol/vtc/account_support
-STM
Red Hat
Pro
650 points
Darren,
That's not an unusual message. Generally, when you run graphical programs, like system-config-authentication, you do so from the applications menu from the desktop environment. STDOUT and STDERR from those applications is not viewable when launched from the desktop environment. However, when you run the command from the command-line, the same is not true. From the command-line, STDOUT and STDERR are sent to the calling terminal window. I've noticed that a lot of graphical applications are chatty when using the terminal, I'd guess a debug mechanism used by the developers. I've seen all kind of information there, from a log of mouse movements to authentication errors. If the tool is working as expected, I wouldn't pay much attention to console content provided by graphical applications. If the application really encounters an error, it will produce an error window and present the error message.
-Scott
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.