3.3. Using OAuth Authentication


As an alternative to basic authentication, limited OAuth 1.0 authentication is supported in the API (this is sometimes referred to as 1-legged OAuth in version 1.0a of the protocol).

3.3.1. Configuring OAuth

OAuth is enabled by default in Satellite 6.3. The configuration settings are stored in the /etc/foreman/settings.yaml configuration file and can be viewed in the web UI by going to Administer Settings Auth. The OAuth consumer key is the token to be used by all OAuth clients. Certain values in the web UI cannot be changed. These values can only be changed by running the satellite-installer script again with the new options. Note that any manual changes to the file will be lost when upgrading. Enter the following command to see all the OAuth related installer options:
# satellite-installer --full-help | grep oauth
If you want all API requests made using OAuth to be authorized as the built-in anonymous API administrator account, then keep OAuth map users set to false in the /etc/foreman/settings.yaml file. If you want to specify the user under which the request is made, change this configuration option to true. This allows clients to send a FOREMAN-USER header with the login of an existing Foreman user.

Important

The header is not signed in an OAuth request, it can therefore be forged. Anyone with valid consumer key can impersonate any Foreman user.
Red Hat logoGithubRedditYoutubeTwitter

Learn

Try, buy, & sell

Communities

About Red Hat Documentation

We help Red Hat users innovate and achieve their goals with our products and services with content they can trust.

Making open source more inclusive

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. For more details, see the Red Hat Blog.

About Red Hat

We deliver hardened solutions that make it easier for enterprises to work across platforms and environments, from the core datacenter to the network edge.

© 2024 Red Hat, Inc.