Replace inline Chrome SSO config with link to upstream RHEL 9 IDM docs#5036
Conversation
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.
38085bd to
8b667e4
Compare
|
Thanks, @adamruzicka, updated. |
|
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. |
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 :/ |
#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)
#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)
#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)
#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)
#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".
#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)
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
Please cherry-pick my commits into:
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 :)