Skip to content

Replace inline Chrome SSO config with link to upstream RHEL 9 IDM docs#5036

Merged
maximiliankolb merged 1 commit into
theforeman:masterfrom
ofedoren:redirect-to-ipa-for-google
Jul 13, 2026
Merged

Replace inline Chrome SSO config with link to upstream RHEL 9 IDM docs#5036
maximiliankolb merged 1 commit into
theforeman:masterfrom
ofedoren:redirect-to-ipa-for-google

Conversation

@ofedoren

@ofedoren ofedoren commented Jul 9, 2026

Copy link
Copy Markdown
Member

The Chrome-specific command line options (--auth-server-whitelist, --auth-negotiate-delegate-whitelist) were renamed since Chrome 101+. Replace the inline procedure with a prerequisite linking to the RHEL 9 Identity Management documentation, matching the pattern already used for Firefox instead of maintaining the option names.

Moreover, the IdM steps suggest to create a configuration file instead of launching Chrome with those options, so we shouldn't suggest something else.

What changes are you introducing?

Dropping Chrome options workaround for SSO auth in favor of IdM docs to be inline with Firefox procedure.

Why are you introducing these changes? (Explanation, links to references, issues, etc.)

See the commit message.

Anything else to add? (Considerations, potential downsides, alternative solutions you have explored, etc.)

An alternative would be just renaming these options to the actual ones.

Contributor checklists

  • I am okay with my commits getting squashed when you merge this PR.
  • I am familiar with the contributing guidelines.

Please cherry-pick my commits into:

  • Foreman 3.19/Katello 4.21
  • Foreman 3.18/Katello 4.20 (Satellite 6.19)
  • Foreman 3.17/Katello 4.19
  • Foreman 3.16/Katello 4.18 (Satellite 6.18; orcharhino 7.6, 7.7, and 7.8)
  • Foreman 3.15/Katello 4.17
  • Foreman 3.14/Katello 4.16 (Satellite 6.17; orcharhino 7.4; orcharhino 7.5)
  • We do not accept PRs for Foreman older than 3.14.

I've selected all the available versions for cherry-picking, but please tell me if it's not applicable or doesn't make sense in the documentation world :)

@github-actions github-actions Bot added Needs tech review Requires a review from the technical perspective Needs style review Requires a review from docs style/grammar perspective Needs testing Requires functional testing labels Jul 9, 2026
The Chrome-specific command line options (--auth-server-whitelist,
--auth-negotiate-delegate-whitelist) were renamed since Chrome 101+.
Replace the inline procedure with a prerequisite linking to the
RHEL 9 Identity Management documentation, matching the pattern
already used for Firefox instead of maintaining the option names.

Moreover, the IdM steps suggest to create a configuration file
instead of launching Chrome with those options, so we shouldn't
suggest something else.
@ofedoren ofedoren force-pushed the redirect-to-ipa-for-google branch from 38085bd to 8b667e4 Compare July 13, 2026 10:43
@ofedoren

Copy link
Copy Markdown
Member Author

Thanks, @adamruzicka, updated.

@maximiliankolb maximiliankolb left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

style-wise LGTM

@maximiliankolb maximiliankolb added style review done No issues from docs style/grammar perspective tech review done No issues from the technical perspective and removed Needs style review Requires a review from docs style/grammar perspective Needs tech review Requires a review from the technical perspective labels Jul 13, 2026
@ofedoren

Copy link
Copy Markdown
Member Author

Just since it's almost merged: should I then open cherry-picks or is there a somewhat automated way that will be done instead?

@maximiliankolb

Copy link
Copy Markdown
Contributor

Just since it's almost merged: should I then open cherry-picks or is there a somewhat automated way that will be done instead?

The person that merges your PR will also perform the cherry-picks. Unless there are major merge conflicts, the maintainer will just cherry-pick and push to GitHub as indicated by the PR. If there are major merge conflicts, we will ping you and kindly ask you to raise a PR for a specific target branch.

BTW: Does this need separate testing? If not, remove the flag & someone will merge it soon-ish.

@ofedoren

Copy link
Copy Markdown
Member Author

BTW: Does this need separate testing?

Not sure what you mean by that... If you mean we need to actually test those changes out (setup IPA, check the options), then I already did that. But if you need someone else to do that instead of the author, then yeah :/

@maximiliankolb maximiliankolb added testing done No issues from the functional perspective and removed Needs testing Requires functional testing labels Jul 13, 2026
@maximiliankolb maximiliankolb merged commit 95e34c9 into theforeman:master Jul 13, 2026
12 checks passed
maximiliankolb pushed a commit that referenced this pull request Jul 13, 2026
#5036)

The Chrome-specific command line options (--auth-server-whitelist,
--auth-negotiate-delegate-whitelist) were renamed since Chrome 101+.
Replace the inline procedure with a prerequisite linking to the
RHEL 9 Identity Management documentation, matching the pattern
already used for Firefox instead of maintaining the option names.

Moreover, the IdM steps suggest to create a configuration file
instead of launching Chrome with those options, so we shouldn't
suggest something else.

(cherry picked from commit 95e34c9)
maximiliankolb pushed a commit that referenced this pull request Jul 13, 2026
#5036)

The Chrome-specific command line options (--auth-server-whitelist,
--auth-negotiate-delegate-whitelist) were renamed since Chrome 101+.
Replace the inline procedure with a prerequisite linking to the
RHEL 9 Identity Management documentation, matching the pattern
already used for Firefox instead of maintaining the option names.

Moreover, the IdM steps suggest to create a configuration file
instead of launching Chrome with those options, so we shouldn't
suggest something else.

(cherry picked from commit 95e34c9)
maximiliankolb pushed a commit that referenced this pull request Jul 13, 2026
#5036)

The Chrome-specific command line options (--auth-server-whitelist,
--auth-negotiate-delegate-whitelist) were renamed since Chrome 101+.
Replace the inline procedure with a prerequisite linking to the
RHEL 9 Identity Management documentation, matching the pattern
already used for Firefox instead of maintaining the option names.

Moreover, the IdM steps suggest to create a configuration file
instead of launching Chrome with those options, so we shouldn't
suggest something else.

(cherry picked from commit 95e34c9)
maximiliankolb pushed a commit that referenced this pull request Jul 13, 2026
#5036)

The Chrome-specific command line options (--auth-server-whitelist,
--auth-negotiate-delegate-whitelist) were renamed since Chrome 101+.
Replace the inline procedure with a prerequisite linking to the
RHEL 9 Identity Management documentation, matching the pattern
already used for Firefox instead of maintaining the option names.

Moreover, the IdM steps suggest to create a configuration file
instead of launching Chrome with those options, so we shouldn't
suggest something else.

(cherry picked from commit 95e34c9)
maximiliankolb pushed a commit that referenced this pull request Jul 13, 2026
#5036)

The Chrome-specific command line options (--auth-server-whitelist,
--auth-negotiate-delegate-whitelist) were renamed since Chrome 101+.
Replace the inline procedure with a prerequisite linking to the
RHEL 9 Identity Management documentation, matching the pattern
already used for Firefox instead of maintaining the option names.

Moreover, the IdM steps suggest to create a configuration file
instead of launching Chrome with those options, so we shouldn't
suggest something else.

(cherry picked from commit 95e34c9)

Resolved a minor merge conflict while cherry-picking from "master" to
"3.15".
maximiliankolb pushed a commit that referenced this pull request Jul 13, 2026
#5036)

The Chrome-specific command line options (--auth-server-whitelist,
--auth-negotiate-delegate-whitelist) were renamed since Chrome 101+.
Replace the inline procedure with a prerequisite linking to the
RHEL 9 Identity Management documentation, matching the pattern
already used for Firefox instead of maintaining the option names.

Moreover, the IdM steps suggest to create a configuration file
instead of launching Chrome with those options, so we shouldn't
suggest something else.

(cherry picked from commit 95e34c9)

Resolved a minor merge conflict while cherry-picking from "master" to
"3.15".

(cherry picked from commit 6a795a0)
@maximiliankolb

Copy link
Copy Markdown
Contributor

Merged to "master" and cherry-picked:
76670a2..0ef1153 3.19 -> 3.19
e1a32ad..b5a059a 3.18 -> 3.18
a26c674..4b7eca2 3.17 -> 3.17
ef3a529..a51a3ae 3.16 -> 3.16
e82c32c..6a795a0 3.15 -> 3.15 (resolved a minor merge conflict)
b1fa937..3b59d78 3.14 -> 3.14

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

Labels

style review done No issues from docs style/grammar perspective tech review done No issues from the technical perspective testing done No issues from the functional perspective

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants