Project

General

Profile

Actions

Bug #31472

open

Manual: (2.3.0) Instructions for obtaining the 'oauth_consumer_key' and 'oauth_consumer_secret' are out-of-date

Added by Peter Bray over 3 years ago. Updated over 3 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Target version:
-
Difficulty:
Triaged:
No
Fixed in Releases:
Found in Releases:

Description

Reference: https://theforeman.org/manuals/2.3/index.html#3.2.3InstallationScenarios

In section 3.2.3 InstallationScenarios, following the "Standalone Puppetserver" "Command line arguments:" example is the text:

Fill in the OAuth consumer key and secret values from your Foreman instance, retrieve them from Administer > Settings > Authentication, and set the Foreman URLs appropriately.

This was changed for security reasons, I believe around the time of Foreman 2.1.0 (IIRC), and the WebUI now displays "The setting is defined in the configuration file settings.yaml and is read-only" if you hover over the "dots" displayed in the value field.

Consult with the appropriate team members for proper guidance on updating this instruction, but I used:

sudo grep oauth_consumer /etc/foreman/settings.yaml

Regards,
Peter

Actions #1

Updated by Ewoud Kohl van Wijngaarden over 3 years ago

It's slower, but more correct to use foreman-rake config:

foreman.example.com # foreman-rake -- config -k oauth_consumer_key
supersecret
foreman.example.com # foreman-rake -- config -k oauth_consumer_secret
alsosecret

You can also let them print in the same command and then grep the output.

Actions #2

Updated by Peter Bray over 3 years ago

Sorry, I just created the changes and was about to update this issue, when I saw your suggestion.

I think I the procedure needs to be more complex (i.e. two command lines) it should be factored out into its own sub-sub-section/paragraph and referenced - IMHO

Any back to what I was going to report the pull request URL for completeness.

https://github.com/theforeman/theforeman.org/pull/1743

Actions

Also available in: Atom PDF