Organization Administrators can directly manage authentication security protocols for Red Hat services through the authentication requirements of your company's single sign-on system.

Single sign-on provides a better authentication experience for users, as users themselves can maintain one less set of login credentials. Currently, company single sign-on integration has the following scope:

• Link the same company IdP with multiple Red Hat accounts.
• Link one company user identity with one Red Hat user identity.
• Use corporate SSO/IdP to authenticate to the Red Hat Customer Portal or any Red Hat application with a web-based authentication flow which uses the Red Hat single sign-on system.
• Support for OpenID Connect (OIDC).
• Support for Security Assertion Markup Language (SAML).

Existing Red Hat users can authenticate to Red Hat with their company single sign-on credentials when their company SSO is integrated with Red Hat SSO.

You can integrate your identity provider with Red Hat SSO by using the self-service identity provider integration support.

Self-service SSO integration is supported for the following Red Hat account types:

• A Red Hat Corporate account type with an active, non-evaluation subscription.
• An approved Red Hat partner account type.

When you integrate your identity provider (IdP) or single sign-on (SSO) with the Red Hat single sign-on to create a federated SSO, any user who cannot authenticate your SSO also cannot authenticate to any Red Hat service with a web-based authentication flow.

A limited number of Red Hat services do not use web-based authentication; these services are not compatible with single sign-on. This means you can revoke a user’s corporate customer IdP credentials, but they can still use their Red Hat account username and password to authenticate to Red Hat services that do not use web-based authentication.

To remove access to all Red Hat services, the Organization Administrator must use the user management tool to deactivate a Red Hat user account. A deactivated account can no longer be used to access any Red Hat service.

Users without accounts in the customer IdP will not be able to authenticate. For example, this can affect vendor/partner relationships where today the vendor/partner user has a Red Hat login within the customer’s Red Hat company account. Once company single sign-on is enabled, if the customer is not able to allow the vendor/partner user to have an account in the customer IdP, the vendor/partner user will no longer be able to log in.

Once integrated, you can use your company single sign-on to login to your Red Hat account.

Log in with company single sign-on.
Company single sign-on is required to access your account.