Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Review & edit AD direct integration ext auth user story #3056

Closed

Conversation

asteflova
Copy link
Contributor

@asteflova asteflova commented Jun 3, 2024

A follow-up on #2938: The goal is to cover the AD user story from beginning to end and make sure it's easy to read and follow.

Also, a follow-up on #2737 which I'm taking over from @adamlazik1.

Please cherry-pick my commits into:

  • Foreman 3.11/Katello 4.13
  • Foreman 3.10/Katello 4.12
  • Foreman 3.9/Katello 4.11 (Satellite 6.15; orcharhino 6.8)
  • Foreman 3.8/Katello 4.10
  • Foreman 3.7/Katello 4.9 (Satellite 6.14)
  • Foreman 3.6/Katello 4.8
  • Foreman 3.5/Katello 4.7 (Satellite 6.13; orcharhino 6.6/6.7)
  • Foreman 3.4/Katello 4.6 (EL8 only)
  • Foreman 3.3/Katello 4.5 on EL7 & EL8 (Satellite 6.12 on EL8 only; orcharhino 6.4/6.5 on EL8 only)
  • We do not accept PRs for Foreman older than 3.3.

. Install the required packages:
+
[options="nowrap", subs="+quotes,verbatim,attributes"]
----
# {project-package-install} sssd adcli realmd ipa-python-compat krb5-workstation samba-common-tools
# {project-package-install} adcli ipa-python-compat krb5-workstation oddjob oddjob-mkhomedir realmd samba-common-tools sssd
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@asteflova
Copy link
Contributor Author

While reviewing the existing docs with SSSD Engineering, we noticed that the existing procedures use both Samba and SSSD to integrate with AD. That’s something that deserves a closer look because SSSD "should" be enough to perform the join and it seems impractical to use both.

This is why I’m going to pause my efforts in reviewing the whole scenario and close this PR. For the immediate future, I’ll only focus on fixing bugs that we currently track for the existing procedures and also on minor doc improvements, such as introductions. I’ll open a new PR for that. I want to keep this one as is for future reference.

@asteflova asteflova closed this Jul 18, 2024
@ekohl
Copy link
Member

ekohl commented Jul 18, 2024

This is why I’m going to pause my efforts in reviewing the whole scenario and close this PR. For the immediate future, I’ll only focus on fixing bugs that we currently track for the existing procedures and also on minor doc improvements, such as introductions. I’ll open a new PR for that. I want to keep this one as is for future reference.

Should we open an issue to be reminded of it?

@asteflova
Copy link
Contributor Author

Should we open an issue to be reminded of it?

I have one downstream: https://issues.redhat.com/browse/SAT-26039 Let me know if that's not enough.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants