이 콘텐츠는 선택한 언어로 제공되지 않습니다.

Chapter 4. Technology Preview


This section lists Technology Preview features in Red Hat Developer Hub 1.5.

Important

Technology Preview features provide early access to upcoming product innovations, enabling you to test functionality and provide feedback during the development process. However, these features are not fully supported under Red Hat Subscription Level Agreements, may not be functionally complete, and are not intended for production use. As Red Hat considers making future iterations of Technology Preview features generally available, we will attempt to resolve any issues that customers experience when using these features. See: Technology Preview support scope.

4.1. Extensions for Red Hat and community plugins

The new Extensions feature enables you to browse available Red Hat and community plugins. The initial version displays all plugins and includes filtering options. Future updates will introduce additional features, such as installation directly from the front-end.

For more information about Extensions, see Extensions in Red Hat Developer Hub.

Additional resources

4.2. Loading authentication providers from dynamic plugins

In Red Hat Developer Hub 1.5, loading authentication providers or modules from dynamic plugins is available as a Technology Preview feature, enabling greater flexibility and customization. The key improvements include:

  • Environment variable control:

    • A new ENABLE_AUTH_PROVIDER_MODULE_OVERRIDE environment variable determines whether the backend installs the default authentication provider module.
    • When the new environment variable is enabled, dynamic plugins can be used to supply custom authentication providers.
  • Custom sign-in page support:

    • A new signInPage configuration allows front-end dynamic plugins to provide a custom SignInPage component.

      Example configuration

      dynamicPlugins:
       frontend:
         my-plugin-package:
           signInPage:
             importName: CustomSignInPage

    • The exported CustomSignInPage will be mapped to components.SignInPage during front-end initialization.
  • Authentication provider settings:

    • A new providerSettings configuration field allows front-end dynamic plugins to define authentication provider settings for display in the Authentication Providers tab on the Settings page.

      Example configuration

      dynamicPlugins:
       frontend:
         my-plugin-package:
           providerSettings:
      - title: Github Two
      description: Sign in with GitHub Org Two
      provider: core.auth.github-two

    • Each providerSettings entry creates a corresponding row in the Authentication Providers tab. The provider field must match the string used in createApiRef when defining the API reference:

      Example configuration

      export const ghTwoAuthApiRef: ApiRef<
       OAuthApi & ProfileInfoApi & BackstageIdentityApi & SessionApi
      > = createApiRef({
       id: 'core.auth.github-two', // <--- this string
      })

For more information, see Authentication in Red Hat Developer Hub.

Red Hat logoGithubredditYoutubeTwitter

자세한 정보

평가판, 구매 및 판매

커뮤니티

Red Hat 문서 정보

Red Hat을 사용하는 고객은 신뢰할 수 있는 콘텐츠가 포함된 제품과 서비스를 통해 혁신하고 목표를 달성할 수 있습니다. 최신 업데이트를 확인하세요.

보다 포괄적 수용을 위한 오픈 소스 용어 교체

Red Hat은 코드, 문서, 웹 속성에서 문제가 있는 언어를 교체하기 위해 최선을 다하고 있습니다. 자세한 내용은 다음을 참조하세요.Red Hat 블로그.

Red Hat 소개

Red Hat은 기업이 핵심 데이터 센터에서 네트워크 에지에 이르기까지 플랫폼과 환경 전반에서 더 쉽게 작업할 수 있도록 강화된 솔루션을 제공합니다.

Theme

© 2026 Red Hat
맨 위로 이동