Red Hat as a sign-in provider
Applications can offer Red Hat as an OAuth sign-in option alongside existing social and enterprise providers.
From the changelog: Red Hat as a sign-in provider
Authdog Team
Teams that already live in Red Hat accounts should not invent a second password for your app. Hosted sign-in already offered social and enterprise OAuth connections. Red Hat is now a first-class provider in that same catalog, so users can sign in with the Red Hat SSO they already have.
This is the longer note behind the August 19 changelog entry.
How it works
Red Hat is an OAuth 2.0 connection, same shape as the other providers on Authentication > Providers. Authdog redirects the user to Red Hat, exchanges the authorization code, reads the profile, and creates or links an Authdog user. Your application receives an Authdog session. It does not handle Red Hat tokens.
The connection is stored per environment. Enabling Red Hat in dev does not enable it in prod. Each environment has its own client credentials and its own callback URL.
The hosted Account Portal shows Red Hat next to the other active connections. Custom UIs that already render the provider list pick it up the same way.
Set it up
In the Authdog console, select the project and environment, then open Authentication > Providers:
- Filter to OAuth 2.0 and find Red Hat.
- Enable the connection.
- Copy the Redirect URI shown in the form into the Red Hat OAuth application allowlist.
- Paste the client ID and client secret from Red Hat.
- Save, mark the connection active, and complete a sign-in on the hosted Account Portal.
The generic connector steps live in Connectors. Recheck the callback URL if you later attach a custom domain; the redirect URI must match what the connection form currently shows.
Trust boundaries
Red Hat authenticates the user at Red Hat. Authdog trusts the tokens it receives for that connection's client credentials. Store the client secret only in Authdog. A misconfigured redirect URI fails at the provider, not inside your app.
A Red Hat sign-in is not an Authdog directory role and is not an AuthZEN decision. Map groups or claims after the session exists if you need authorization.
Keep environment credentials separate. A leaked dev secret does not unlock production if production uses its own client.
Try it
Enable Red Hat on a non-production environment, then sign in from the hosted Account Portal. Provider setup is in Connectors. The original release note is in the changelog.