Uploaded image for project: 'Product Technical Learning'
  1. Product Technical Learning
  2. PTL-7314

RH362-66: Ch 5 AD direct connection needs to be split or trimmed. Too long!

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Major Major
    • RH362 - RHEL 9.1 0, RH362 - RHEL 7.4 1 20180531
    • RH362
    • ILT
    • en-US (English)

      URL:
      Reporter RHNID:
      Section: -
      Language: en-US (English)
      Workaround:

      Description: Accessing Active Directory Using Direct Integration

      This whole narration section is 14 pages. That is just TOO much.

      And IG expects it to be covered in 20 minutes. HA!

      "Selecting a Direct Integration Method" can be enhanced a bit to show use cases for each method. You say what each can and cannot do but not much on what scenarios would really need anything other than using sssd.

      Also, you mention sssd, Native LDAP, and winbind but then you describe sssd, realmd, and winbind so the category splits are mixed.

      "Using SSSD for Direct Integration" seems like it should be the core of this section but appears to heavily mimic the published docs. Perhaps it can be summarized more. Especially the components that are setup automatically with the realm command!

      "Using realmd for Direct Integration" is the part that matches the hands on so it should be the bulk of the narration.

      "Using Samba for Direct Integration" should be minimized to explaining the use case and all implantation should be left to the product documentation. There are some good use cases described here that are worth keeping. The winbind portion should also be removed from the GE since we do not have any requirements for it in our lab environment.

            rht-pagomez Patrick Gomez
            lauber Susan Lauber
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: