Skip to main content

このバージョンの GitHub Enterprise サーバーはこの日付をもって終了となります: 2023-12-20. 重大なセキュリティの問題に対してであっても、パッチリリースは作成されません。 パフォーマンスの向上、セキュリティの向上、新機能の向上を図るために、最新バージョンの GitHub Enterprise サーバーにアップグレードしてください。 アップグレードに関するヘルプについては、GitHub Enterprise サポートにお問い合わせください

管理コンソールへのアクセスの管理

が [Management Console] にアクセスしたり、[Management Console] 認証レート制限を構成したりできます。

About access to the Management Console

From the Management Console, you can initialize, configure, and monitor your GitHub Enterprise Server instance. For more information, see "About the Management Console."

You can access the Management Console using the Management Console password. An administrator created the password during the initial setup process for your GitHub Enterprise Server instance. For more information about Management Console access, see "Administering your instance from the web UI."

Configuring rate limits for authentication to the Management Console

You can configure the lockout time and login attempt limits for the Management Console. If you configure rate limits, the limits apply to both the root site administrator and any Management Console users.

After you configure rate limits and a user exceeds the limit, the Management Console will remain locked for the duration set by the lockout time. To immediately unlock access to the Management Console, use the ghe-reactivate-admin-login command via the administrative shell. For more information, see "Command-line utilities" and "Accessing the administrative shell (SSH)."

  1. From an administrative account on GitHub Enterprise Server, in the upper-right corner of any page, click .

  2. If you're not already on the "Site admin" page, in the upper-left corner, click Site admin.

  3. In the " Site admin" sidebar, click Management Console.

  4. Optionally, under "Lockout time", type a number of minutes to lock the Management Console after too many failed login attempts.

  5. Optionally, under "Login attempt limit", type a maximum number of failed login attempts to allow before the Management Console is locked.

  6. Under the "Settings" sidebar, click Save settings.

    Note: Saving settings in the Management Console restarts system services, which could result in user-visible downtime.

  7. Wait for the configuration run to complete.