Sorry if this is an obvious one, but I'm trying to be as safe as possible
with my production environment.
I'm connecting a freshly installed smart proxy to my newly upgraded 1.9.3
Foreman server. I noticed that oauth is currently disabled
(oauth_active=False), and no keys have been set.
Is it safe to just enable oauth? We have a number of services that access
the API via username/password. I want to be confident that doing this
won't break them.
Also, how do I go about generating the
oauth_consumer_key/oauth_consumer_secret? I've typically used the
foreman-installer for my development environments, and the key has been
generated automatically. I'm wondering if there's an easy way to go back
after the fact, and generate the key and secret in the same way.
Thanks.
> Sorry if this is an obvious one, but I'm trying to be as safe as
> possible with my production environment.
>
> I'm connecting a freshly installed smart proxy to my newly upgraded
> 1.9.3 Foreman server. I noticed that oauth is currently disabled
> (oauth_active=False), and no keys have been set.
>
> Is it safe to just enable oauth? We have a number of services that
> access the API via username/password. I want to be confident that doing
> this won't break them.
It's safe, it's only an additional auth mechanism.
> Also, how do I go about generating the
> oauth_consumer_key/oauth_consumer_secret? I've typically used the
> foreman-installer for my development environments, and the key has been
> generated automatically. I'm wondering if there's an easy way to go
> back after the fact, and generate the key and secret in the same way.
The installer simply generates two 32-character strings for both the key
and secret, I'd suggest just doing something similar.
If you're using the installer then running it with defaults should set
it up, or delete the oauth entries from the answers file and it'll
regenerate them.
···
On 21/12/15 23:09, Kyle Flavin wrote:
–
Dominic Cleal
dominic@cleal.org
