diff --git a/.github/workflows/staging-deploy-pr.yml b/.github/workflows/staging-deploy-pr.yml index ed5de66b1230..f4c35296e7df 100644 --- a/.github/workflows/staging-deploy-pr.yml +++ b/.github/workflows/staging-deploy-pr.yml @@ -36,14 +36,6 @@ env: BUILD_ACTIONS_RUN_LOG: https://github.com/${{ github.repository }}/actions/runs/${{ github.event.workflow_run.id }} jobs: - debug: - runs-on: ubuntu-latest - steps: - - name: Dump full context for debugging - env: - GITHUB_CONTEXT: ${{ toJSON(github) }} - run: echo "$GITHUB_CONTEXT" - pr-metadata: # This is needed because the workflow we depend on # (see on.workflow_run.workflows) might be running from pushes on diff --git a/lib/page.js b/lib/page.js index 1b822831a91c..7d02c5825140 100644 --- a/lib/page.js +++ b/lib/page.js @@ -13,7 +13,6 @@ import renderContent from './render-content/index.js' import processLearningTracks from './process-learning-tracks.js' import { productMap } from './all-products.js' import slash from 'slash' -import statsd from './statsd.js' import readFileContents from './read-file-contents.js' import getLinkData from './get-link-data.js' import getDocumentType from './get-document-type.js' @@ -114,9 +113,7 @@ class Page { this.showMiniToc = this.showMiniToc === false ? this.showMiniToc : true } - // Instrument the `_render` method, so externally we call #render - // but it's wrapped in a timer that reports to Datadog - this.render = statsd.asyncTimer(this._render.bind(this), 'page.render') + this.render = this._render.bind(this) return this } diff --git a/middleware/index.js b/middleware/index.js index 9eed341a14a3..60919f6bdb50 100644 --- a/middleware/index.js +++ b/middleware/index.js @@ -34,6 +34,7 @@ import helpToDocs from './redirects/help-to-docs.js' import languageCodeRedirects from './redirects/language-code-redirects.js' import handleRedirects from './redirects/handle-redirects.js' import findPage from './find-page.js' +import spotContentFlaws from './spot-content-flaws.js' import blockRobots from './block-robots.js' import archivedEnterpriseVersionsAssets from './archived-enterprise-versions-assets.js' import events from './events.js' @@ -173,6 +174,7 @@ export default function (app) { // *** Config and context for rendering *** app.use(asyncMiddleware(instrument(findPage, './find-page'))) // Must come before archived-enterprise-versions, breadcrumbs, featured-links, products, render-page + app.use(asyncMiddleware(instrument(spotContentFlaws, './spot-content-flaws'))) // Must come after findPage app.use(instrument(blockRobots, './block-robots')) // Check for a dropped connection before proceeding diff --git a/middleware/render-page.js b/middleware/render-page.js index 149417ba18f9..47ac9a8bc712 100644 --- a/middleware/render-page.js +++ b/middleware/render-page.js @@ -2,11 +2,10 @@ import { get } from 'lodash-es' import patterns from '../lib/patterns.js' import getMiniTocItems from '../lib/get-mini-toc-items.js' import Page from '../lib/page.js' +import statsd from '../lib/statsd.js' import { isConnectionDropped } from './halt-on-dropped-connection.js' import { nextApp, nextHandleRequest } from './next.js' -const pageCache = new Map() - export default async function renderPage(req, res, next) { if (req.path.startsWith('/storybook')) { return nextHandleRequest(req, res) @@ -31,45 +30,6 @@ export default async function renderPage(req, res, next) { // Is the request for JSON debugging info? const isRequestingJsonForDebugging = 'json' in req.query && process.env.NODE_ENV !== 'production' - // ****** temporary caching measure for holiday spam prevention ********* - - const isApiPage = - req.context.currentPathWithoutLanguage.includes('rest/reference') || - req.context.currentPathWithoutLanguage.includes('graphql/reference') - - // Serve from the cache if possible - const isCacheable = - // Skip for CI - !process.env.CI && - // Skip for tests - process.env.NODE_ENV !== 'test' && - // Skip for HTTP methods other than GET - req.method === 'GET' && - // Skip for JSON debugging info requests - !isRequestingJsonForDebugging && - // Only API pages - isApiPage - - // don't cache query strings - const originalUrl = req.originalUrl.split('?')[0] - - if (isCacheable) { - // Stop processing if the connection was already dropped - if (isConnectionDropped(req, res)) return - - const cachedHtml = pageCache.get(originalUrl) - if (cachedHtml) { - // Stop processing if the connection was already dropped - if (isConnectionDropped(req, res)) return - - console.log(`Serving from cached version of ${originalUrl}`) - // statsd.increment('page.sent_from_cache') - return res.send(cachedHtml) - } - } - - // ****** [end] temporary caching measure for holiday spam prevention ********* - // add page context const context = Object.assign({}, req.context, { page }) @@ -88,7 +48,10 @@ export default async function renderPage(req, res, next) { if (isConnectionDropped(req, res)) return // render page - context.renderedPage = await page.render(context) + const pageRenderTimed = statsd.asyncTimer(page.render, 'middleware.render_page', [ + `path:${req.pagePath || req.path}`, + ]) + context.renderedPage = await pageRenderTimed(context) // Stop processing if the connection was already dropped if (isConnectionDropped(req, res)) return @@ -145,12 +108,5 @@ export default async function renderPage(req, res, next) { // Hand rendering over to NextJS req.context.renderedPage = context.renderedPage req.context.miniTocItems = context.miniTocItems - - // ****** temporary caching measure for holiday spam prevention ********* - if (isCacheable) { - pageCache.set(originalUrl, req.context.renderedPage) - } - // ****** [end] temporary caching measure for holiday spam prevention ********* - return nextHandleRequest(req, res) } diff --git a/middleware/spot-content-flaws.js b/middleware/spot-content-flaws.js new file mode 100644 index 000000000000..d05ce4c1f6b8 --- /dev/null +++ b/middleware/spot-content-flaws.js @@ -0,0 +1,32 @@ +// This middleware, exclusively in 'development' tries to spot flaws in +// the content you're actively viewing. +// The hopeful assumption is that if you're actively viewing this +// page on localhost, you're actively working on its content. + +import path from 'path' + +import kleur from 'kleur' + +export default async function spotContentFlaws(req, res, next) { + const { page } = req.context + if (process.env.NODE_ENV === 'development' && page) { + const trailingSlashRedirects = (page.redirect_from || []).filter( + (uri) => uri.endsWith('/') && uri.startsWith('/') + ) + if (trailingSlashRedirects.length > 0) { + console.warn( + `The page ${kleur.bold(path.relative(process.cwd(), page.fullPath))} has ${ + trailingSlashRedirects.length + } redirect_from entries that have a trailing slash\n ${kleur.yellow( + trailingSlashRedirects.join('\n ') + )}` + ) + console.log( + "If you're actively working on this page, consider", + kleur.bold('deleting all trailing slashes in redirect_from.\n') + ) + } + } + + return next() +} diff --git a/package-lock.json b/package-lock.json index 4c024ca009ca..2e8f3b9a759e 100644 --- a/package-lock.json +++ b/package-lock.json @@ -47,6 +47,7 @@ "imurmurhash": "^0.1.4", "js-cookie": "^3.0.1", "js-yaml": "^4.1.0", + "kleur": "4.1.4", "liquidjs": "^9.22.1", "lodash": "^4.17.21", "lodash-es": "^4.17.21", @@ -13371,10 +13372,9 @@ } }, "node_modules/kleur": { - "version": "3.0.3", - "resolved": "https://registry.npmjs.org/kleur/-/kleur-3.0.3.tgz", - "integrity": "sha512-eTIzlVOSUR+JxdDFepEYcBMtZ9Qqdef+rnzWdRZuMbOywu5tO2w2N7rqjoANZ5k9vywhL6Br1VRjUIgTQx4E8w==", - "devOptional": true, + "version": "4.1.4", + "resolved": "https://registry.npmjs.org/kleur/-/kleur-4.1.4.tgz", + "integrity": "sha512-8QADVssbrFjivHWQU7KkMgptGTl6WAcSdlbBPY4uNF+mWr6DGcKrvY2w4FQJoXch7+fKMjj0dRrL75vk3k23OA==", "engines": { "node": ">=6" } @@ -17831,6 +17831,15 @@ "node": ">= 6" } }, + "node_modules/prompts/node_modules/kleur": { + "version": "3.0.3", + "resolved": "https://registry.npmjs.org/kleur/-/kleur-3.0.3.tgz", + "integrity": "sha512-eTIzlVOSUR+JxdDFepEYcBMtZ9Qqdef+rnzWdRZuMbOywu5tO2w2N7rqjoANZ5k9vywhL6Br1VRjUIgTQx4E8w==", + "devOptional": true, + "engines": { + "node": ">=6" + } + }, "node_modules/prop-types": { "version": "15.7.2", "resolved": "https://registry.npmjs.org/prop-types/-/prop-types-15.7.2.tgz", @@ -22247,14 +22256,6 @@ "node": ">=8" } }, - "node_modules/uvu/node_modules/kleur": { - "version": "4.1.4", - "resolved": "https://registry.npmjs.org/kleur/-/kleur-4.1.4.tgz", - "integrity": "sha512-8QADVssbrFjivHWQU7KkMgptGTl6WAcSdlbBPY4uNF+mWr6DGcKrvY2w4FQJoXch7+fKMjj0dRrL75vk3k23OA==", - "engines": { - "node": ">=6" - } - }, "node_modules/v8-compile-cache": { "version": "2.3.0", "resolved": "https://registry.npmjs.org/v8-compile-cache/-/v8-compile-cache-2.3.0.tgz", @@ -33493,10 +33494,9 @@ "integrity": "sha512-dcS1ul+9tmeD95T+x28/ehLgd9mENa3LsvDTtzm3vyBEO7RPptvAD+t44WVXaUjTBRcrpFeFlC8WCruUR456hw==" }, "kleur": { - "version": "3.0.3", - "resolved": "https://registry.npmjs.org/kleur/-/kleur-3.0.3.tgz", - "integrity": "sha512-eTIzlVOSUR+JxdDFepEYcBMtZ9Qqdef+rnzWdRZuMbOywu5tO2w2N7rqjoANZ5k9vywhL6Br1VRjUIgTQx4E8w==", - "devOptional": true + "version": "4.1.4", + "resolved": "https://registry.npmjs.org/kleur/-/kleur-4.1.4.tgz", + "integrity": "sha512-8QADVssbrFjivHWQU7KkMgptGTl6WAcSdlbBPY4uNF+mWr6DGcKrvY2w4FQJoXch7+fKMjj0dRrL75vk3k23OA==" }, "language-subtag-registry": { "version": "0.3.21", @@ -36869,6 +36869,14 @@ "requires": { "kleur": "^3.0.3", "sisteransi": "^1.0.5" + }, + "dependencies": { + "kleur": { + "version": "3.0.3", + "resolved": "https://registry.npmjs.org/kleur/-/kleur-3.0.3.tgz", + "integrity": "sha512-eTIzlVOSUR+JxdDFepEYcBMtZ9Qqdef+rnzWdRZuMbOywu5tO2w2N7rqjoANZ5k9vywhL6Br1VRjUIgTQx4E8w==", + "devOptional": true + } } }, "prop-types": { @@ -40276,13 +40284,6 @@ "kleur": "^4.0.3", "sade": "^1.7.3", "totalist": "^2.0.0" - }, - "dependencies": { - "kleur": { - "version": "4.1.4", - "resolved": "https://registry.npmjs.org/kleur/-/kleur-4.1.4.tgz", - "integrity": "sha512-8QADVssbrFjivHWQU7KkMgptGTl6WAcSdlbBPY4uNF+mWr6DGcKrvY2w4FQJoXch7+fKMjj0dRrL75vk3k23OA==" - } } }, "v8-compile-cache": { diff --git a/package.json b/package.json index c9c70c070ef8..c1960a4dcfa7 100644 --- a/package.json +++ b/package.json @@ -49,6 +49,7 @@ "imurmurhash": "^0.1.4", "js-cookie": "^3.0.1", "js-yaml": "^4.1.0", + "kleur": "4.1.4", "liquidjs": "^9.22.1", "lodash": "^4.17.21", "lodash-es": "^4.17.21", diff --git a/translations/ja-JP/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/disabling-unauthenticated-sign-ups.md b/translations/ja-JP/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/disabling-unauthenticated-sign-ups.md index 98825fdc5700..3711fe5ef60f 100644 --- a/translations/ja-JP/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/disabling-unauthenticated-sign-ups.md +++ b/translations/ja-JP/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/disabling-unauthenticated-sign-ups.md @@ -1,11 +1,11 @@ --- -title: 認証のないサインアップの無効化 +title: Disabling unauthenticated sign-ups redirect_from: - - /enterprise/admin/articles/disabling-sign-ups/ + - /enterprise/admin/articles/disabling-sign-ups - /enterprise/admin/user-management/disabling-unauthenticated-sign-ups - /enterprise/admin/authentication/disabling-unauthenticated-sign-ups - /admin/authentication/disabling-unauthenticated-sign-ups -intro: ビルトイン認証を使っている場合、認証されていない人がアカウントを作成するのをブロックできます。 +intro: 'If you''re using built-in authentication, you can block unauthenticated people from being able to create an account.' versions: ghes: '*' type: how_to @@ -15,9 +15,9 @@ topics: - Enterprise shortTitle: Block account creation --- - {% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} {% data reusables.enterprise_management_console.privacy %} -3. **Enable sign-up（サインアップの有効化）**の選択を外してください。 ![[Enable sign-up] チェックボックス](/assets/images/enterprise/management-console/enable-sign-up.png) +3. Unselect **Enable sign-up**. +![Enable sign-up checkbox](/assets/images/enterprise/management-console/enable-sign-up.png) {% data reusables.enterprise_management_console.save-settings %} diff --git a/translations/ja-JP/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/index.md b/translations/ja-JP/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/index.md index 57b99c5b36cf..5d51187af03b 100644 --- a/translations/ja-JP/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/index.md +++ b/translations/ja-JP/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/index.md @@ -1,11 +1,11 @@ --- -title: GitHub Enterprise Server インスタンスでユーザを認証する -intro: '{% data variables.product.prodname_ghe_server %} のビルトイン認証を使うか、CAS、LDAP、SAML のいずれかを選択して既存のアカウントを統合し、{% data variables.product.product_location %} へのユーザアクセスを集中管理できます。' +title: Authenticating users for your GitHub Enterprise Server instance +intro: 'You can use {% data variables.product.prodname_ghe_server %}''s built-in authentication, or choose between CAS, LDAP, or SAML to integrate your existing accounts and centrally manage user access to {% data variables.product.product_location %}.' redirect_from: - - /enterprise/admin/categories/authentication/ - - /enterprise/admin/guides/installation/user-authentication/ - - /enterprise/admin/articles/inviting-users/ - - /enterprise/admin/guides/migrations/authenticating-users-for-your-github-enterprise-instance/ + - /enterprise/admin/categories/authentication + - /enterprise/admin/guides/installation/user-authentication + - /enterprise/admin/articles/inviting-users + - /enterprise/admin/guides/migrations/authenticating-users-for-your-github-enterprise-instance - /enterprise/admin/user-management/authenticating-users-for-your-github-enterprise-server-instance - /enterprise/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance versions: diff --git a/translations/ja-JP/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/using-cas.md b/translations/ja-JP/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/using-cas.md index 1d2495dcb62e..b1276f2de730 100644 --- a/translations/ja-JP/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/using-cas.md +++ b/translations/ja-JP/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/using-cas.md @@ -1,12 +1,12 @@ --- -title: CASの利用 +title: Using CAS redirect_from: - - /enterprise/admin/articles/configuring-cas-authentication/ - - /enterprise/admin/articles/about-cas-authentication/ + - /enterprise/admin/articles/configuring-cas-authentication + - /enterprise/admin/articles/about-cas-authentication - /enterprise/admin/user-management/using-cas - /enterprise/admin/authentication/using-cas - /admin/authentication/using-cas -intro: 'CAS は、複数の Web アプリケーションのためのシングルサインオン (SSO) プロトコルです。 CASのユーザアカウントは、ユーザがサインインするまで{% ifversion ghes %}ユーザライセンス{% else %}シート{% endif %}を消費しません。' +intro: 'CAS is a single sign-on (SSO) protocol for multiple web applications. A CAS user account does not take up a {% ifversion ghes %}user license{% else %}seat{% endif %} until the user signs in.' versions: ghes: '*' type: how_to @@ -17,10 +17,9 @@ topics: - Identity - SSO --- - {% data reusables.enterprise_user_management.built-in-authentication %} -## CASでのユーザ名についての考慮 +## Username considerations with CAS {% data reusables.enterprise_management_console.username_normalization %} @@ -29,24 +28,25 @@ topics: {% data reusables.enterprise_user_management.two_factor_auth_header %} {% data reusables.enterprise_user_management.external_auth_disables_2fa %} -## CASの属性 +## CAS attributes -以下の属性が利用できます。 +The following attributes are available. -| 属性名 | 種類 | 説明 | -| ------ | -- | -------------------------------------------------------- | -| `ユーザ名` | 必須 | {% data variables.product.prodname_ghe_server %} のユーザ名 | +| Attribute name | Type | Description | +|--------------------------|----------|-------------| +| `username` | Required | The {% data variables.product.prodname_ghe_server %} username. | -## CASの設定 +## Configuring CAS {% warning %} -**警告：**{% data variables.product.product_location %}でCASを設定するまでは、ユーザはCASのユーザ名とパスワードをAPIリクエストの認証やHTTP/HTTPS経由のGit操作に使えないことに注意してください。 その代わりに、ユーザは[アクセストークンを作成](/enterprise/{{ currentVersion }}/user/articles/creating-an-access-token-for-command-line-use)しなければなりません。 +**Warning:** Before configuring CAS on {% data variables.product.product_location %}, note that users will not be able to use their CAS usernames and passwords to authenticate API requests or Git operations over HTTP/HTTPS. Instead, they will need to [create an access token](/enterprise/{{ currentVersion }}/user/articles/creating-an-access-token-for-command-line-use). {% endwarning %} {% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} {% data reusables.enterprise_management_console.authentication %} -3. **CAS**を選択してください。 ![CAS の選択](/assets/images/enterprise/management-console/cas-select.png) -4. {% data reusables.enterprise_user_management.built-in-authentication-option %} ![CAS ビルトイン認証の選択チェックボックス](/assets/images/enterprise/management-console/cas-built-in-authentication.png) -5. **Server URL（サーバのURL）**フィールドにCASサーバの完全なURLを入力してください。 CAS サーバが {% data variables.product.prodname_ghe_server %} が検証できない証明書を使っているなら、`ghe-ssl-ca-certificate-install` を使えばその証明書を信頼済みの証明書としてインストールできます。 +3. Select **CAS**. +![CAS select](/assets/images/enterprise/management-console/cas-select.png) +4. {% data reusables.enterprise_user_management.built-in-authentication-option %} ![Select CAS built-in authentication checkbox](/assets/images/enterprise/management-console/cas-built-in-authentication.png) +5. In the **Server URL** field, type the full URL of your CAS server. If your CAS server uses a certificate that can't be validated by {% data variables.product.prodname_ghe_server %}, you can use the `ghe-ssl-ca-certificate-install` command to install it as a trusted certificate. diff --git a/translations/ja-JP/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/using-ldap.md b/translations/ja-JP/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/using-ldap.md index a7d55a8a1686..77d922b9e82c 100644 --- a/translations/ja-JP/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/using-ldap.md +++ b/translations/ja-JP/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/using-ldap.md @@ -1,11 +1,11 @@ --- title: Using LDAP redirect_from: - - /enterprise/admin/articles/configuring-ldap-authentication/ - - /enterprise/admin/articles/about-ldap-authentication/ - - /enterprise/admin/articles/viewing-ldap-users/ - - /enterprise/admin/hidden/enabling-ldap-sync/ - - /enterprise/admin/hidden/ldap-sync/ + - /enterprise/admin/articles/configuring-ldap-authentication + - /enterprise/admin/articles/about-ldap-authentication + - /enterprise/admin/articles/viewing-ldap-users + - /enterprise/admin/hidden/enabling-ldap-sync + - /enterprise/admin/hidden/ldap-sync - /enterprise/admin/user-management/using-ldap - /enterprise/admin/authentication/using-ldap - /admin/authentication/using-ldap diff --git a/translations/ja-JP/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/using-saml.md b/translations/ja-JP/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/using-saml.md index b7f582ffcb9f..33cd83f62b16 100644 --- a/translations/ja-JP/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/using-saml.md +++ b/translations/ja-JP/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/using-saml.md @@ -1,8 +1,8 @@ --- title: Using SAML redirect_from: - - /enterprise/admin/articles/configuring-saml-authentication/ - - /enterprise/admin/articles/about-saml-authentication/ + - /enterprise/admin/articles/configuring-saml-authentication + - /enterprise/admin/articles/about-saml-authentication - /enterprise/admin/user-management/using-saml - /enterprise/admin/authentication/using-saml - /admin/authentication/using-saml diff --git a/translations/ja-JP/content/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/index.md b/translations/ja-JP/content/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/index.md index d41f097870ef..c82069b7a4c8 100644 --- a/translations/ja-JP/content/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/index.md +++ b/translations/ja-JP/content/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/index.md @@ -4,7 +4,7 @@ shortTitle: Manage users with your IdP product: '{% data reusables.gated-features.emus %}' intro: You can manage identity and access with your identity provider and provision accounts that can only contribute to your enterprise. redirect_from: - - /github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/ + - /github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider versions: ghec: '*' topics: diff --git a/translations/ja-JP/content/admin/configuration/configuring-network-settings/configuring-a-hostname.md b/translations/ja-JP/content/admin/configuration/configuring-network-settings/configuring-a-hostname.md index 5b30214ee06e..2727ae6ddc07 100644 --- a/translations/ja-JP/content/admin/configuration/configuring-network-settings/configuring-a-hostname.md +++ b/translations/ja-JP/content/admin/configuration/configuring-network-settings/configuring-a-hostname.md @@ -1,8 +1,8 @@ --- -title: ホスト名の設定 -intro: アプライアンスには、ハードコードされたIPアドレスを使うのではなくホスト名を設定することをおすすめします。 +title: Configuring a hostname +intro: We recommend setting a hostname for your appliance instead of using a hard-coded IP address. redirect_from: - - /enterprise/admin/guides/installation/configuring-hostnames/ + - /enterprise/admin/guides/installation/configuring-hostnames - /enterprise/admin/installation/configuring-a-hostname - /enterprise/admin/configuration/configuring-a-hostname - /admin/configuration/configuring-a-hostname @@ -14,19 +14,20 @@ topics: - Fundamentals - Infrastructure --- +If you configure a hostname instead of a hard-coded IP address, you will be able to change the physical hardware that {% data variables.product.product_location %} runs on without affecting users or client software. -ハードコードされたIPアドレスの代わりにホスト名を設定すれば、ユーザやクライアントソフトウェアに影響を与えることなく{% data variables.product.product_location %}を動作させる物理ハードウェアを変更できるようになります。 - -{% data variables.enterprise.management_console %} のホスト名の設定は、適切な完全修飾ドメイン名 (FQDN) に設定して、インターネット上または内部ネットワーク内で解決できるようにしてください。 たとえば、ホスト名の設定は `github.companyname.com` であるかもしれません。 また、選択したホスト名に対して Subdomain Isolation を有効にして、いくつかのクロスサイトスクリプティングスタイルの脆弱性を軽減することもおすすめします。 ホスト名の設定に関する詳しい情報については、[HTTP RFC の Section 2.1](https://tools.ietf.org/html/rfc1123#section-2) を参照してください。 +The hostname setting in the {% data variables.enterprise.management_console %} should be set to an appropriate fully qualified domain name (FQDN) which is resolvable on the internet or within your internal network. For example, your hostname setting could be `github.companyname.com.` We also recommend enabling subdomain isolation for the chosen hostname to mitigate several cross-site scripting style vulnerabilities. For more information on hostname settings, see [Section 2.1 of the HTTP RFC](https://tools.ietf.org/html/rfc1123#section-2). {% data reusables.enterprise_installation.changing-hostname-not-supported %} {% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} {% data reusables.enterprise_management_console.hostname-menu-item %} -4. {% data variables.product.product_location %} に設定するホスト名を入力します。 ![ホスト名を設定するためのフィールド](/assets/images/enterprise/management-console/hostname-field.png) -5. 新しいホスト名のためのDNS及びSSLの設定をテストするには**Test domain settings（ドメイン設定のテスト）**をクリックしてください。 ![[Test domain settings] ボタン](/assets/images/enterprise/management-console/test-domain-settings.png) +4. Type the hostname you'd like to set for {% data variables.product.product_location %}. + ![Field for setting a hostname](/assets/images/enterprise/management-console/hostname-field.png) +5. To test the DNS and SSL settings for the new hostname, click **Test domain settings**. + ![Test domain settings button](/assets/images/enterprise/management-console/test-domain-settings.png) {% data reusables.enterprise_management_console.test-domain-settings-failure %} {% data reusables.enterprise_management_console.save-settings %} -ホスト名を設定したら、{% data variables.product.product_location %}のSubdomain Isolationを有効化することをお勧めします。 詳しい情報については"[Subdomain Isolationの有効化](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-subdomain-isolation/)"を参照してください。 +After you configure a hostname, we recommend that you enable subdomain isolation for {% data variables.product.product_location %}. For more information, see "[Enabling subdomain isolation](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-subdomain-isolation/)." diff --git a/translations/ja-JP/content/admin/configuration/configuring-network-settings/configuring-an-outbound-web-proxy-server.md b/translations/ja-JP/content/admin/configuration/configuring-network-settings/configuring-an-outbound-web-proxy-server.md index de124e0d390f..efcd3a1f2d2a 100644 --- a/translations/ja-JP/content/admin/configuration/configuring-network-settings/configuring-an-outbound-web-proxy-server.md +++ b/translations/ja-JP/content/admin/configuration/configuring-network-settings/configuring-an-outbound-web-proxy-server.md @@ -1,8 +1,8 @@ --- -title: アウトバウンドのWebプロキシサーバの設定 -intro: 'プロキシサーバは、{% data variables.product.product_location %}に追加のセキュリティのレベルをもたらしてくれます。' +title: Configuring an outbound web proxy server +intro: 'A proxy server provides an additional level of security for {% data variables.product.product_location %}.' redirect_from: - - /enterprise/admin/guides/installation/configuring-a-proxy-server/ + - /enterprise/admin/guides/installation/configuring-a-proxy-server - /enterprise/admin/installation/configuring-an-outbound-web-proxy-server - /enterprise/admin/configuration/configuring-an-outbound-web-proxy-server - /admin/configuration/configuring-an-outbound-web-proxy-server @@ -19,23 +19,25 @@ shortTitle: Configure an outbound proxy ## About proxies with {% data variables.product.product_name %} -{% data variables.product.product_location %} に対してプロキシサーバーが有効である場合、送信先ホストが HTTP プロキシ除外として追加されていない限り、{% data variables.product.prodname_ghe_server %} によって送信されたアウトバウンドメッセージがプロキシサーバーを経由してまず最初に送信されます。 アウトバウンドのメッセージの種類には、webhook、Bundleのアップロード、レガシーのアバターのフェッチが含まれます。 プロキシサーバのURLは、たとえば`http://127.0.0.1:8123`といったように、プロトコル、ドメインもしくはIPアドレスにポート番号を加えたものです。 +When a proxy server is enabled for {% data variables.product.product_location %}, outbound messages sent by {% data variables.product.prodname_ghe_server %} are first sent through the proxy server, unless the destination host is added as an HTTP proxy exclusion. Types of outbound messages include outgoing webhooks, uploading bundles, and fetching legacy avatars. The proxy server's URL is the protocol, domain or IP address, plus the port number, for example `http://127.0.0.1:8123`. {% note %} -**メモ:** {% data variables.product.product_location %}　を　{% data variables.product.prodname_dotcom_the_website %} に接続するには、`github.com` と `api.github.com` への接続がプロキシ設定で許可されている必要があります。 For more information, see "[Connecting your enterprise account to {% data variables.product.prodname_dotcom_the_website %}](/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud)." +**Note:** To connect {% data variables.product.product_location %} to {% data variables.product.prodname_dotcom_the_website %}, your proxy configuration must allow connectivity to `github.com` and `api.github.com`. For more information, see "[Connecting your enterprise account to {% data variables.product.prodname_dotcom_the_website %}](/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud)." {% endnote %} {% data reusables.actions.proxy-considerations %} For more information about using {% data variables.product.prodname_actions %} with {% data variables.product.prodname_ghe_server %}, see "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_server %}](/admin/github-actions/enabling-github-actions-for-github-enterprise-server/getting-started-with-github-actions-for-github-enterprise-server)." -## アウトバウンドのWebプロキシサーバの設定 +## Configuring an outbound web proxy server {% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} {% data reusables.enterprise_management_console.privacy %} -1. **HTTP Proxy Server（HTTPプロキシサーバ）**の下に、プロキシサーバのURLを入力してください。 ![HTTP プロキシサーバーのURLを入力するためのフィールド](/assets/images/enterprise/management-console/http-proxy-field.png) - -5. オプションで、プロキシのアクセスを要しないホストがあれば**HTTP Proxy Exclusion（HTTPプロキシの除外）**の下にカンマ区切りで入力してください。 ドメイン内のすべてのホストをプロキシアクセスの要求から除外するには `.` をワイルドカードプレフィックスとして使用できます。 たとえば、`.octo-org.tentacle` などです。 ![HTTP プロキシの除外を入力するためのフィールド](/assets/images/enterprise/management-console/http-proxy-exclusion-field.png) +1. Under **HTTP Proxy Server**, type the URL of your proxy server. + ![Field to type the HTTP Proxy Server URL](/assets/images/enterprise/management-console/http-proxy-field.png) + +5. Optionally, under **HTTP Proxy Exclusion**, type any hosts that do not require proxy access, separating hosts with commas. To exclude all hosts in a domain from requiring proxy access, you can use `.` as a wildcard prefix. For example: `.octo-org.tentacle` + ![Field to type any HTTP Proxy Exclusions](/assets/images/enterprise/management-console/http-proxy-exclusion-field.png) {% data reusables.enterprise_management_console.save-settings %} diff --git a/translations/ja-JP/content/admin/configuration/configuring-network-settings/configuring-built-in-firewall-rules.md b/translations/ja-JP/content/admin/configuration/configuring-network-settings/configuring-built-in-firewall-rules.md index 1ff199294d80..b6f5cbfb9d16 100644 --- a/translations/ja-JP/content/admin/configuration/configuring-network-settings/configuring-built-in-firewall-rules.md +++ b/translations/ja-JP/content/admin/configuration/configuring-network-settings/configuring-built-in-firewall-rules.md @@ -1,8 +1,8 @@ --- -title: 組み込みファイアウォールのルール設定 -intro: '{% data variables.product.product_location %}のデフォルトのファイアウォールのルールとカスタマイズされたルールを見ることができます。' +title: Configuring built-in firewall rules +intro: 'You can view default firewall rules and customize rules for {% data variables.product.product_location %}.' redirect_from: - - /enterprise/admin/guides/installation/configuring-firewall-settings/ + - /enterprise/admin/guides/installation/configuring-firewall-settings - /enterprise/admin/installation/configuring-built-in-firewall-rules - /enterprise/admin/configuration/configuring-built-in-firewall-rules - /admin/configuration/configuring-built-in-firewall-rules @@ -16,19 +16,18 @@ topics: - Networking shortTitle: Configure firewall rules --- +## About {% data variables.product.product_location %}'s firewall -## {% data variables.product.product_location %}のファイアウォールについて +{% data variables.product.prodname_ghe_server %} uses Ubuntu's Uncomplicated Firewall (UFW) on the virtual appliance. For more information see "[UFW](https://help.ubuntu.com/community/UFW)" in the Ubuntu documentation. {% data variables.product.prodname_ghe_server %} automatically updates the firewall allowlist of allowed services with each release. -{% data variables.product.prodname_ghe_server %} は、仮想アプライアンスで Ubuntu の Uncomplicated Firewall (UFW) を使用します。 詳しい情報についてはUbuntuのドキュメンテーションの"[UFW](https://help.ubuntu.com/community/UFW)"を参照してください。 {% data variables.product.prodname_ghe_server %} は、許可されたサービスのファイアウォールのホワイトリストをリリースごとに自動的に更新します。 +After you install {% data variables.product.prodname_ghe_server %}, all required network ports are automatically opened to accept connections. Every non-required port is automatically configured as `deny`, and the default outgoing policy is configured as `allow`. Stateful tracking is enabled for any new connections; these are typically network packets with the `SYN` bit set. For more information, see "[Network ports](/enterprise/admin/guides/installation/network-ports)." -{% data variables.product.prodname_ghe_server %} をインストールすると、接続を受け入れるために必要なすべてのネットワークポートが自動的に開かれます。 不必要なすべてのポートは自動的に`deny`に設定され、デフォルトの送信ポリシーは`allow`に設定されます。 ステートフルな追跡は、任意の新しいコネクションに対して有効化されます。それらは通常、`SYN`ビットが立てられているネットワークパケットです。 詳しい情報については"[ネットワークポート](/enterprise/admin/guides/installation/network-ports)"を参照してください。 +The UFW firewall also opens several other ports that are required for {% data variables.product.prodname_ghe_server %} to operate properly. For more information on the UFW rule set, see [the UFW README](https://bazaar.launchpad.net/~jdstrand/ufw/0.30-oneiric/view/head:/README#L213). -UFW ファイアウォールは、{% data variables.product.prodname_ghe_server %} が正しく動作するのに必要となる他のいくつかのポートも開きます。 UFW のルールセットに関する詳しい情報については、[the UFW README](https://bazaar.launchpad.net/~jdstrand/ufw/0.30-oneiric/view/head:/README#L213) を参照してください。 - -## デフォルトのファイアウォールルールの表示 +## Viewing the default firewall rules {% data reusables.enterprise_installation.ssh-into-instance %} -2. デフォルトのファイアウォールルールを表示するには、`sudo ufw status` コマンドを使用します。 以下と同じような出力が表示されるでしょう: +2. To view the default firewall rules, use the `sudo ufw status` command. You should see output similar to this: ```shell $ sudo ufw status > Status: active @@ -56,46 +55,46 @@ UFW ファイアウォールは、{% data variables.product.prodname_ghe_server > ghe-9418 (v6) ALLOW Anywhere (v6) ``` -## カスタムのファイアウォールルールの追加 +## Adding custom firewall rules {% warning %} -**警告:** 既知の作業状態にリセットする必要が生じた場合に備えて、カスタムのファイアウォールルールを追加する前に、現在のルールをバックアップしてください。 サーバーからロックアウトされている場合には、{% data variables.contact.contact_ent_support %}に問い合わせて、元のファイアウォールルールを再設定してください。 元のファイアウォールルールを復元すると、サーバーでダウンタイムが発生します。 +**Warning:** Before you add custom firewall rules, back up your current rules in case you need to reset to a known working state. If you're locked out of your server, contact {% data variables.contact.contact_ent_support %} to reconfigure the original firewall rules. Restoring the original firewall rules involves downtime for your server. {% endwarning %} -1. カスタムのファイアウォールルールを設定する。 -2. `status numbered`コマンドを使って、新しいルールそれぞれのステータスをチェックします。 +1. Configure a custom firewall rule. +2. Check the status of each new rule with the `status numbered` command. ```shell $ sudo ufw status numbered ``` -3. カスタムのファイアウォールルールをバックアップするには、`cp` コマンドを使用してルールを新しいファイルに移動します。 +3. To back up your custom firewall rules, use the `cp`command to move the rules to a new file. ```shell $ sudo cp -r /etc/ufw ~/ufw.backup ``` -{% data variables.product.product_location %}をアップグレードした後は、カスタムのファイアウォールルールを再適用しなければなりません。 ファイアウォールのカスタムルールを再適用するためのスクリプトを作成することをお勧めします。 +After you upgrade {% data variables.product.product_location %}, you must reapply your custom firewall rules. We recommend that you create a script to reapply your firewall custom rules. -## デフォルトのファイアウォールルールのリストア +## Restoring the default firewall rules -ファイアウォールルールの変更後に何か問題が生じたなら、オリジナルのバックアップからルールをリセットできます。 +If something goes wrong after you change the firewall rules, you can reset the rules from your original backup. {% warning %} -**警告:** ファイアウォールに変更を加える前にオリジナルのルールをバックアップしていなかった場合は、{% data variables.contact.contact_ent_support %} にお問い合わせください。 +**Warning:** If you didn't back up the original rules before making changes to the firewall, contact {% data variables.contact.contact_ent_support %} for further assistance. {% endwarning %} {% data reusables.enterprise_installation.ssh-into-instance %} -2. 以前のバックアップルールを復元するには、`cp` コマンドでそれらをファイアウォールにコピーして戻します。 +2. To restore the previous backup rules, copy them back to the firewall with the `cp` command. ```shell $ sudo cp -f ~/ufw.backup/*rules /etc/ufw ``` -3. `systemctl` コマンドでファイアウォールを再起動します。 +3. Restart the firewall with the `systemctl` command. ```shell $ sudo systemctl restart ufw ``` -4. `ufw status` コマンドで、ルールがデフォルトに戻っていることを確認します。 +4. Confirm that the rules are back to their defaults with the `ufw status` command. ```shell $ sudo ufw status > Status: active diff --git a/translations/ja-JP/content/admin/configuration/configuring-network-settings/configuring-dns-nameservers.md b/translations/ja-JP/content/admin/configuration/configuring-network-settings/configuring-dns-nameservers.md index 9282ecde8ab3..0080d55693c3 100644 --- a/translations/ja-JP/content/admin/configuration/configuring-network-settings/configuring-dns-nameservers.md +++ b/translations/ja-JP/content/admin/configuration/configuring-network-settings/configuring-dns-nameservers.md @@ -1,8 +1,8 @@ --- -title: DNSネームサーバの設定 -intro: '{% data variables.product.prodname_ghe_server %} は、動的ホスト構成プロトコル (DHCP) のリースがネームサーバーを提供するときに、DNS 設定に対して DHCP を使用します。 ネームサーバがDHCPのリースで提供されない場合、あるいは特定のDNS設定を使う必要がある場合は、手動でネームサーバを指定できます。' +title: Configuring DNS nameservers +intro: '{% data variables.product.prodname_ghe_server %} uses the dynamic host configuration protocol (DHCP) for DNS settings when DHCP leases provide nameservers. If nameservers are not provided by a dynamic host configuration protocol (DHCP) lease, or if you need to use specific DNS settings, you can specify the nameservers manually.' redirect_from: - - /enterprise/admin/guides/installation/about-dns-nameservers/ + - /enterprise/admin/guides/installation/about-dns-nameservers - /enterprise/admin/installation/configuring-dns-nameservers - /enterprise/admin/configuration/configuring-dns-nameservers - /admin/configuration/configuring-dns-nameservers @@ -16,26 +16,25 @@ topics: - Networking shortTitle: Configure DNS servers --- - -指定するネームサーバは、{% data variables.product.product_location %}のホスト名を解決できなければなりません。 +The nameservers you specify must resolve {% data variables.product.product_location %}'s hostname. {% data reusables.enterprise_installation.changing-hostname-not-supported %} -## 仮想マシンのコンソールを使ったネームサーバの設定 +## Configuring nameservers using the virtual machine console {% data reusables.enterprise_installation.open-vm-console-start %} -2. インスタンスに対してネームサーバーを設定します。 +2. Configure nameservers for your instance. {% data reusables.enterprise_installation.vm-console-done %} -## 管理シェルを使ったネームサーバの設定 +## Configuring nameservers using the administrative shell {% data reusables.enterprise_installation.ssh-into-instance %} -2. ネームサーバーを編集するには、次を入力します: +2. To edit your nameservers, enter: ```shell $ sudo vim /etc/resolvconf/resolv.conf.d/head ``` -3. `nameserver` エントリを追加し、続いてファイルを保存します。 -4. 変更を確認したら、ファイルを保存します。 +3. Append any `nameserver` entries, then save the file. +4. After verifying your changes, save the file. 5. To add your new nameserver entries to {% data variables.product.product_location %}, run the following: ```shell $ sudo service resolvconf restart diff --git a/translations/ja-JP/content/admin/configuration/configuring-network-settings/configuring-tls.md b/translations/ja-JP/content/admin/configuration/configuring-network-settings/configuring-tls.md index 48293c4994b9..e3a251095cc2 100644 --- a/translations/ja-JP/content/admin/configuration/configuring-network-settings/configuring-tls.md +++ b/translations/ja-JP/content/admin/configuration/configuring-network-settings/configuring-tls.md @@ -1,9 +1,9 @@ --- -title: TLSの設定 -intro: '信頼できる認証機関によって署名された証明書を使用できるように、{% data variables.product.product_location %} で Transport Layer Security (TLS) を設定できます。' +title: Configuring TLS +intro: 'You can configure Transport Layer Security (TLS) on {% data variables.product.product_location %} so that you can use a certificate that is signed by a trusted certificate authority.' redirect_from: - - /enterprise/admin/articles/ssl-configuration/ - - /enterprise/admin/guides/installation/about-tls/ + - /enterprise/admin/articles/ssl-configuration + - /enterprise/admin/guides/installation/about-tls - /enterprise/admin/installation/configuring-tls - /enterprise/admin/configuration/configuring-tls - /admin/configuration/configuring-tls @@ -17,53 +17,55 @@ topics: - Networking - Security --- +## About Transport Layer Security -## Transport Layer Securityについて +TLS, which replaced SSL, is enabled and configured with a self-signed certificate when {% data variables.product.prodname_ghe_server %} is started for the first time. As self-signed certificates are not trusted by web browsers and Git clients, these clients will report certificate warnings until you disable TLS or upload a certificate signed by a trusted authority, such as Let's Encrypt. -SSL に代わる TLS は、{% data variables.product.prodname_ghe_server %} の初回起動時に有効になり、自己署名証明書で設定されます。 自己署名証明書は Web ブラウザや Git クライアントから信頼されていないため、TLS を無効にするか、Let's Encrypt などの信頼できる機関によって署名された証明書をアップロードするまで、これらのクライアントは証明書の警告を報告します。 - -SSL が有効な場合、{% data variables.product.prodname_ghe_server %} アプライアンスは HTTP Strict Transport Security ヘッダーを送信します。 TLSを無効化すると、ブラウザはHTTPへのプロトコルダウングレードを許さないので、ユーザはアプライアンスにアクセスできなくなります。 詳しい情報についてはWikipediaの"[HTTP Strict Transport Security](https://ja.wikipedia.org/wiki/HTTP_Strict_Transport_Security)"を参照してください。 +The {% data variables.product.prodname_ghe_server %} appliance will send HTTP Strict Transport Security headers when SSL is enabled. Disabling TLS will cause users to lose access to the appliance, because their browsers will not allow a protocol downgrade to HTTP. For more information, see "[HTTP Strict Transport Security (HSTS)](https://en.wikipedia.org/wiki/HTTP_Strict_Transport_Security)" on Wikipedia. {% data reusables.enterprise_installation.terminating-tls %} -ユーザが2要素認証のFIDO U2Fを利用できるようにするには、インスタンスでTLSを有効化しなければなりません。 詳しい情報については「[2 要素認証の設定](/articles/configuring-two-factor-authentication)」を参照してください。 +To allow users to use FIDO U2F for two-factor authentication, you must enable TLS for your instance. For more information, see "[Configuring two-factor authentication](/articles/configuring-two-factor-authentication)." -## 必要な環境 +## Prerequisites -プロダクションでTLSを利用するには、暗号化されていないPEMフォーマットで、信頼済みの証明書認証局によって署名された証明書がなければなりません。 +To use TLS in production, you must have a certificate in an unencrypted PEM format signed by a trusted certificate authority. -また、証明書には"[Subdomain Isolationの有効化](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-subdomain-isolation#about-subdomain-isolation)"のリストにあるサブドメインに設定されたSubject Alternative Namesが必要で、中間証明書認証局によって署名されたものであれば、完全な証明書チェーンを含んでいる必要があります。 詳しい情報についてはWikipediaの"[Subject Alternative Name](http://en.wikipedia.org/wiki/SubjectAltName)"を参照してください。 +Your certificate will also need Subject Alternative Names configured for the subdomains listed in "[Enabling subdomain isolation](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-subdomain-isolation#about-subdomain-isolation)" and will need to include the full certificate chain if it has been signed by an intermediate certificate authority. For more information, see "[Subject Alternative Name](http://en.wikipedia.org/wiki/SubjectAltName)" on Wikipedia. -`ghe-ssl-generate-csr` コマンドを使用すれば、インスタンス用の証明書署名要求 (CSR) を生成できます。 詳細は「[コマンドラインユーティリティ](/enterprise/{{ currentVersion }}/admin/guides/installation/command-line-utilities/#ghe-ssl-generate-csr)」を参照してください。 +You can generate a certificate signing request (CSR) for your instance using the `ghe-ssl-generate-csr` command. For more information, see "[Command-line utilities](/enterprise/{{ currentVersion }}/admin/guides/installation/command-line-utilities/#ghe-ssl-generate-csr)." -## カスタムのTLS証明書のアップロード +## Uploading a custom TLS certificate {% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} {% data reusables.enterprise_management_console.privacy %} {% data reusables.enterprise_management_console.select-tls-only %} -4. [TLS Protocol support] で、許可するプロトコルを選択します。 ![TLS プロトコルを選択するオプションを備えたラジオボタン](/assets/images/enterprise/management-console/tls-protocol-support.png) -5. "Certificate（証明書）"の下で**Choose File（ファイルの選択）**をクリックし、インストールしたいTLS証明書もしくは証明書チェーン（PEMフォーマット）を選択してください。 このファイルは通常、*.pem*、*.crt*、*.cer* といった拡張子を持ちます。 ![TLS 証明書ファイルを見つけるためのボタン](/assets/images/enterprise/management-console/install-tls-certificate.png) -6. Under "Unencrypted key", click **Choose File** to choose an RSA key (in PEM format) to install. このファイルは通常*.key*という拡張子を持ちます。 ![TLS鍵ファイルを見つけるためのボタン](/assets/images/enterprise/management-console/install-tls-key.png) +4. Under "TLS Protocol support", select the protocols you want to allow. + ![Radio buttons with options to choose TLS protocols](/assets/images/enterprise/management-console/tls-protocol-support.png) +5. Under "Certificate", click **Choose File** to choose a TLS certificate or certificate chain (in PEM format) to install. This file will usually have a *.pem*, *.crt*, or *.cer* extension. + ![Button to find TLS certificate file](/assets/images/enterprise/management-console/install-tls-certificate.png) +6. Under "Unencrypted key", click **Choose File** to choose an RSA key (in PEM format) to install. This file will usually have a *.key* extension. + ![Button to find TLS key file](/assets/images/enterprise/management-console/install-tls-key.png) {% warning %} - **Warning**: Your key must be an RSA key and must not have a passphrase. 詳しい情報については"[キーファイルからのパスフレーズの除去](/admin/guides/installation/troubleshooting-ssl-errors#removing-the-passphrase-from-your-key-file)"を参照してください。 + **Warning**: Your key must be an RSA key and must not have a passphrase. For more information, see "[Removing the passphrase from your key file](/admin/guides/installation/troubleshooting-ssl-errors#removing-the-passphrase-from-your-key-file)". {% endwarning %} {% data reusables.enterprise_management_console.save-settings %} -## Let's Encryptのサポートについて +## About Let's Encrypt support -Let's Encryptは公開の証明書認証者で、ACMEプロトコルを使ってブラウザが信頼するTLS証明書を、無料で自動的に発行してくれます。 アプライアンスのためのLet's Encryptの証明書は、手動のメンテナンスを必要とせず自動的に取得及び更新できます。 +Let's Encrypt is a public certificate authority that issues free, automated TLS certificates that are trusted by browsers using the ACME protocol. You can automatically obtain and renew Let's Encrypt certificates on your appliance without any required manual maintenance. {% data reusables.enterprise_installation.lets-encrypt-prerequisites %} -Let's Encryptを使ったTLS証明書管理の自動化を有効にすると、{% data variables.product.product_location %}はLet's Encryptのサーバに接続して証明書を取得します。 証明書を更新するには、Let's EncryptのサーバはインバウンドのHTTPリクエストで設定されたドメイン名の制御を検証しなければなりません。 +When you enable automation of TLS certificate management using Let's Encrypt, {% data variables.product.product_location %} will contact the Let's Encrypt servers to obtain a certificate. To renew a certificate, Let's Encrypt servers must validate control of the configured domain name with inbound HTTP requests. -また、{% data variables.product.product_location %}上でコマンドラインユーティリティの`ghe-ssl-acme`を使っても、自動的にLet's Encryptの証明書を生成できます。 詳細は「[コマンドラインユーティリティ](/enterprise/{{ currentVersion }}/admin/guides/installation/command-line-utilities#ghe-ssl-acme)」を参照してください。 +You can also use the `ghe-ssl-acme` command line utility on {% data variables.product.product_location %} to automatically generate a Let's Encrypt certificate. For more information, see "[Command-line utilities](/enterprise/{{ currentVersion }}/admin/guides/installation/command-line-utilities#ghe-ssl-acme)." -## Let's Encryptを使ったTLSの設定 +## Configuring TLS using Let's Encrypt {% data reusables.enterprise_installation.lets-encrypt-prerequisites %} @@ -71,9 +73,12 @@ Let's Encryptを使ったTLS証明書管理の自動化を有効にすると、{ {% data reusables.enterprise_site_admin_settings.management-console %} {% data reusables.enterprise_management_console.privacy %} {% data reusables.enterprise_management_console.select-tls-only %} -5. **Enable automation of TLS certificate management using Let's Encrypt（Let's Encryptを使った自動的なTLS証明書管理の有効化）**を選択してください。 ![[Let's Encrypt] を有効化するチェックボックス](/assets/images/enterprise/management-console/lets-encrypt-checkbox.png) +5. Select **Enable automation of TLS certificate management using Let's Encrypt**. + ![Checkbox to enable Let's Encrypt](/assets/images/enterprise/management-console/lets-encrypt-checkbox.png) {% data reusables.enterprise_management_console.save-settings %} {% data reusables.enterprise_management_console.privacy %} -7. **Request TLS certificate（TLS証明書のリクエスト）**をクリックしてください。 ![[Request TLS certificate] ボタン](/assets/images/enterprise/management-console/request-tls-button.png) -8. Wait for the "Status" to change from "STARTED" to "DONE". ![Let's Encrypt status](/assets/images/enterprise/management-console/lets-encrypt-status.png) -9. **Save configuration（設定の保存）**をクリックしてください。 +7. Click **Request TLS certificate**. + ![Request TLS certificate button](/assets/images/enterprise/management-console/request-tls-button.png) +8. Wait for the "Status" to change from "STARTED" to "DONE". + ![Let's Encrypt status](/assets/images/enterprise/management-console/lets-encrypt-status.png) +9. Click **Save configuration**. diff --git a/translations/ja-JP/content/admin/configuration/configuring-network-settings/enabling-subdomain-isolation.md b/translations/ja-JP/content/admin/configuration/configuring-network-settings/enabling-subdomain-isolation.md index 73d567594916..24d09e4f831a 100644 --- a/translations/ja-JP/content/admin/configuration/configuring-network-settings/enabling-subdomain-isolation.md +++ b/translations/ja-JP/content/admin/configuration/configuring-network-settings/enabling-subdomain-isolation.md @@ -1,8 +1,8 @@ --- -title: Subdomain Isolationの有効化 -intro: 'Subdomain Isolation をセットアップすれば、ユーザーが提供したコンテンツを {% data variables.product.prodname_ghe_server %} アプライアンスの他の部分から安全に分離できるようになります。' +title: Enabling subdomain isolation +intro: 'You can set up subdomain isolation to securely separate user-supplied content from other portions of your {% data variables.product.prodname_ghe_server %} appliance.' redirect_from: - - /enterprise/admin/guides/installation/about-subdomain-isolation/ + - /enterprise/admin/guides/installation/about-subdomain-isolation - /enterprise/admin/installation/enabling-subdomain-isolation - /enterprise/admin/configuration/enabling-subdomain-isolation - /admin/configuration/enabling-subdomain-isolation @@ -17,49 +17,49 @@ topics: - Security shortTitle: Enable subdomain isolation --- +## About subdomain isolation -## Subdomain Isolationについて +Subdomain isolation mitigates cross-site scripting and other related vulnerabilities. For more information, see "[Cross-site scripting](http://en.wikipedia.org/wiki/Cross-site_scripting)" on Wikipedia. We highly recommend that you enable subdomain isolation on {% data variables.product.product_location %}. -Subdomain Isolationは、クロスサイトスクリプティングや関連するその他の脆弱性を緩和します。 詳しい情報については"Wikipediaの[クロスサイトスクリプティング](http://en.wikipedia.org/wiki/Cross-site_scripting)"を参照してください。 {% data variables.product.product_location %}ではSubdomain Isolationを有効化することを強くお勧めします。 +When subdomain isolation is enabled, {% data variables.product.prodname_ghe_server %} replaces several paths with subdomains. After enabling subdomain isolation, attempts to access the previous paths for some user-supplied content, such as `http(s)://HOSTNAME/raw/`, may return `404` errors. -Subdomain Isolation が有効な場合、{% data variables.product.prodname_ghe_server %} はいくつかのパスをサブドメインで置き換えます。 After enabling subdomain isolation, attempts to access the previous paths for some user-supplied content, such as `http(s)://HOSTNAME/raw/`, may return `404` errors. +| Path without subdomain isolation | Path with subdomain isolation | +| --- | --- | +| `http(s)://HOSTNAME/assets/` | `http(s)://assets.HOSTNAME/` | +| `http(s)://HOSTNAME/avatars/` | `http(s)://avatars.HOSTNAME/` | +| `http(s)://HOSTNAME/codeload/` | `http(s)://codeload.HOSTNAME/` | +| `http(s)://HOSTNAME/gist/` | `http(s)://gist.HOSTNAME/` | +| `http(s)://HOSTNAME/media/` | `http(s)://media.HOSTNAME/` | +| `http(s)://HOSTNAME/pages/` | `http(s)://pages.HOSTNAME/` | +| `http(s)://HOSTNAME/raw/` | `http(s)://raw.HOSTNAME/` | +| `http(s)://HOSTNAME/render/` | `http(s)://render.HOSTNAME/` | +| `http(s)://HOSTNAME/reply/` | `http(s)://reply.HOSTNAME/` | +| `http(s)://HOSTNAME/uploads/` | `http(s)://uploads.HOSTNAME/` | {% ifversion ghes %} +| `https://HOSTNAME/_registry/docker/` | `http(s)://docker.HOSTNAME/`{% endif %}{% ifversion ghes %} +| `https://HOSTNAME/_registry/npm/` | `https://npm.HOSTNAME/` +| `https://HOSTNAME/_registry/rubygems/` | `https://rubygems.HOSTNAME/` +| `https://HOSTNAME/_registry/maven/` | `https://maven.HOSTNAME/` +| `https://HOSTNAME/_registry/nuget/` | `https://nuget.HOSTNAME/`{% endif %} -| Subdomain Isolationなしのパス | Subdomain Isolationされたパス | -| -------------------------------------- | ----------------------------------------------------------- | -| `http(s)://HOSTNAME/assets/` | `http(s)://assets.HOSTNAME/` | -| `http(s)://HOSTNAME/avatars/` | `http(s)://avatars.HOSTNAME/` | -| `http(s)://HOSTNAME/codeload/` | `http(s)://codeload.HOSTNAME/` | -| `http(s)://HOSTNAME/gist/` | `http(s)://gist.HOSTNAME/` | -| `http(s)://HOSTNAME/media/` | `http(s)://media.HOSTNAME/` | -| `http(s)://HOSTNAME/pages/` | `http(s)://pages.HOSTNAME/` | -| `http(s)://HOSTNAME/raw/` | `http(s)://raw.HOSTNAME/` | -| `http(s)://HOSTNAME/render/` | `http(s)://render.HOSTNAME/` | -| `http(s)://HOSTNAME/reply/` | `http(s)://reply.HOSTNAME/` | -| `http(s)://HOSTNAME/uploads/` | `http(s)://uploads.HOSTNAME/` |{% ifversion ghes %} -| `https://HOSTNAME/_registry/docker/` | `http(s)://docker.HOSTNAME/`{% endif %}{% ifversion ghes %} -| `https://HOSTNAME/_registry/npm/` | `https://npm.HOSTNAME/` | -| `https://HOSTNAME/_registry/rubygems/` | `https://rubygems.HOSTNAME/` | -| `https://HOSTNAME/_registry/maven/` | `https://maven.HOSTNAME/` | -| `https://HOSTNAME/_registry/nuget/` | `https://nuget.HOSTNAME/`{% endif %} - -## 必要な環境 +## Prerequisites {% data reusables.enterprise_installation.disable-github-pages-warning %} -Subdomain Isolationを有効化する前に、新しいドメインに合わせてネットワークを設定しなければなりません。 +Before you enable subdomain isolation, you must configure your network settings for your new domain. -- 有効なドメイン名を、IP アドレスではなくホスト名として指定します。 詳しい情報については、「[ホスト名を設定する](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-a-hostname)」を参照してください。 +- Specify a valid domain name as your hostname, instead of an IP address. For more information, see "[Configuring a hostname](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-a-hostname)." {% data reusables.enterprise_installation.changing-hostname-not-supported %} -- 上記のサブドメインに対して、ワイルドカードのドメインネームシステム (DNS) レコードまたは個々の DNS レコードをセットアップします。 各サブドメイン用に複数のレコードを作成せずに済むよう、サーバのIPアドレスを指す`*.HOSTNAME`のAレコードを作成することをおすすめします。 -- `HOSTNAME` とワイルドカードのドメイン `*.HOSTNAME` の両方に対するサブジェクト代替名 (SAN) が記載された、`*.HOSTNAME` に対するワイルドカードの Transport Layer Security (TLS) 証明書を取得します。 たとえば、ホスト名が `github.octoinc.com` である場合は、Common Name の値が `*.github.octoinc.com` に設定され、SAN の値が `github.octoinc.com` と `*.github.octoinc.com` の両方に設定された証明書を取得します。 -- アプライアンスで TLS を有効にします。 詳しい情報については"[TLSの設定](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-tls/)"を参照してください +- Set up a wildcard Domain Name System (DNS) record or individual DNS records for the subdomains listed above. We recommend creating an A record for `*.HOSTNAME` that points to your server's IP address so you don't have to create multiple records for each subdomain. +- Get a wildcard Transport Layer Security (TLS) certificate for `*.HOSTNAME` with a Subject Alternative Name (SAN) for both `HOSTNAME` and the wildcard domain `*.HOSTNAME`. For example, if your hostname is `github.octoinc.com`, get a certificate with the Common Name value set to `*.github.octoinc.com` and a SAN value set to both `github.octoinc.com` and `*.github.octoinc.com`. +- Enable TLS on your appliance. For more information, see "[Configuring TLS](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-tls/)." -## Subdomain Isolationの有効化 +## Enabling subdomain isolation {% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} {% data reusables.enterprise_management_console.hostname-menu-item %} -4. **Subdomain isolation (recommended)（Subdomain Isolation（推奨））**を選択してください。 ![Subdomain Isolation を有効化するチェックボックス](/assets/images/enterprise/management-console/subdomain-isolation.png) +4. Select **Subdomain isolation (recommended)**. + ![Checkbox to enable subdomain isolation](/assets/images/enterprise/management-console/subdomain-isolation.png) {% data reusables.enterprise_management_console.save-settings %} diff --git a/translations/ja-JP/content/admin/configuration/configuring-network-settings/index.md b/translations/ja-JP/content/admin/configuration/configuring-network-settings/index.md index a29b1da2971b..e3a5d065731b 100644 --- a/translations/ja-JP/content/admin/configuration/configuring-network-settings/index.md +++ b/translations/ja-JP/content/admin/configuration/configuring-network-settings/index.md @@ -1,13 +1,13 @@ --- -title: ネットワークを設定する +title: Configuring network settings redirect_from: - - /enterprise/admin/guides/installation/dns-hostname-subdomain-isolation-and-ssl/ - - /enterprise/admin/articles/about-dns-ssl-and-subdomain-settings/ - - /enterprise/admin/articles/configuring-dns-ssl-and-subdomain-settings/ - - /enterprise/admin/guides/installation/configuring-your-github-enterprise-network-settings/ + - /enterprise/admin/guides/installation/dns-hostname-subdomain-isolation-and-ssl + - /enterprise/admin/articles/about-dns-ssl-and-subdomain-settings + - /enterprise/admin/articles/configuring-dns-ssl-and-subdomain-settings + - /enterprise/admin/guides/installation/configuring-your-github-enterprise-network-settings - /enterprise/admin/installation/configuring-your-github-enterprise-server-network-settings - /enterprise/admin/configuration/configuring-network-settings -intro: 'ネットワークで必要な DNS ネームサーバーとホスト名を使用して {% data variables.product.prodname_ghe_server %} を設定します。 プロキシサーバあるいはファイアウォールルールを設定することもできます。 管理及びユーザのために特定のポートへのアクセスを許可しなければなりません。' +intro: 'Configure {% data variables.product.prodname_ghe_server %} with the DNS nameservers and hostname required in your network. You can also configure a proxy server or firewall rules. You must allow access to certain ports for administrative and user purposes.' versions: ghes: '*' topics: diff --git a/translations/ja-JP/content/admin/configuration/configuring-network-settings/network-ports.md b/translations/ja-JP/content/admin/configuration/configuring-network-settings/network-ports.md index 4fcd17c1a7e1..80cfbb860b31 100644 --- a/translations/ja-JP/content/admin/configuration/configuring-network-settings/network-ports.md +++ b/translations/ja-JP/content/admin/configuration/configuring-network-settings/network-ports.md @@ -1,10 +1,10 @@ --- title: Network ports redirect_from: - - /enterprise/admin/articles/configuring-firewalls/ - - /enterprise/admin/articles/firewall/ - - /enterprise/admin/guides/installation/network-configuration/ - - /enterprise/admin/guides/installation/network-ports-to-open/ + - /enterprise/admin/articles/configuring-firewalls + - /enterprise/admin/articles/firewall + - /enterprise/admin/guides/installation/network-configuration + - /enterprise/admin/guides/installation/network-ports-to-open - /enterprise/admin/installation/network-ports - /enterprise/admin/configuration/network-ports - /admin/configuration/network-ports diff --git a/translations/ja-JP/content/admin/configuration/configuring-network-settings/using-github-enterprise-server-with-a-load-balancer.md b/translations/ja-JP/content/admin/configuration/configuring-network-settings/using-github-enterprise-server-with-a-load-balancer.md index 8f8fdadc5aec..b720b6c9a0f5 100644 --- a/translations/ja-JP/content/admin/configuration/configuring-network-settings/using-github-enterprise-server-with-a-load-balancer.md +++ b/translations/ja-JP/content/admin/configuration/configuring-network-settings/using-github-enterprise-server-with-a-load-balancer.md @@ -2,7 +2,7 @@ title: Using GitHub Enterprise Server with a load balancer intro: 'Use a load balancer in front of a single {% data variables.product.prodname_ghe_server %} appliance or a pair of appliances in a High Availability configuration.' redirect_from: - - /enterprise/admin/guides/installation/using-github-enterprise-with-a-load-balancer/ + - /enterprise/admin/guides/installation/using-github-enterprise-with-a-load-balancer - /enterprise/admin/installation/using-github-enterprise-server-with-a-load-balancer - /enterprise/admin/configuration/using-github-enterprise-server-with-a-load-balancer - /admin/configuration/using-github-enterprise-server-with-a-load-balancer diff --git a/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md b/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md index 2e8a16c34545..2c3a6f3bb846 100644 --- a/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md +++ b/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md @@ -2,8 +2,8 @@ title: Command-line utilities intro: '{% data variables.product.prodname_ghe_server %} includes a variety of utilities to help resolve particular problems or perform specific tasks.' redirect_from: - - /enterprise/admin/articles/viewing-all-services/ - - /enterprise/admin/articles/command-line-utilities/ + - /enterprise/admin/articles/viewing-all-services + - /enterprise/admin/articles/command-line-utilities - /enterprise/admin/installation/command-line-utilities - /enterprise/admin/configuration/command-line-utilities - /admin/configuration/command-line-utilities diff --git a/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/configuring-email-for-notifications.md b/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/configuring-email-for-notifications.md index 908386931e6c..e0987ad3378b 100644 --- a/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/configuring-email-for-notifications.md +++ b/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/configuring-email-for-notifications.md @@ -2,10 +2,10 @@ title: Configuring email for notifications intro: 'To make it easy for users to respond quickly to activity on {% data variables.product.product_name %}, you can configure {% data variables.product.product_location %} to send email notifications for issue, pull request, and commit comments.' redirect_from: - - /enterprise/admin/guides/installation/email-configuration/ - - /enterprise/admin/articles/configuring-email/ - - /enterprise/admin/articles/troubleshooting-email/ - - /enterprise/admin/articles/email-configuration-and-troubleshooting/ + - /enterprise/admin/guides/installation/email-configuration + - /enterprise/admin/articles/configuring-email + - /enterprise/admin/articles/troubleshooting-email + - /enterprise/admin/articles/email-configuration-and-troubleshooting - /enterprise/admin/user-management/configuring-email-for-notifications - /admin/configuration/configuring-email-for-notifications versions: diff --git a/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/configuring-github-pages-for-your-enterprise.md b/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/configuring-github-pages-for-your-enterprise.md index d5d41ee13a7a..d341653ffe6e 100644 --- a/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/configuring-github-pages-for-your-enterprise.md +++ b/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/configuring-github-pages-for-your-enterprise.md @@ -2,12 +2,12 @@ title: Configuring GitHub Pages for your enterprise intro: 'You can enable or disable {% data variables.product.prodname_pages %} for your enterprise{% ifversion ghes %} and choose whether to make sites publicly accessible{% endif %}.' redirect_from: - - /enterprise/admin/guides/installation/disabling-github-enterprise-pages/ - - /enterprise/admin/guides/installation/configuring-github-enterprise-pages/ + - /enterprise/admin/guides/installation/disabling-github-enterprise-pages + - /enterprise/admin/guides/installation/configuring-github-enterprise-pages - /enterprise/admin/installation/configuring-github-pages-on-your-appliance - /enterprise/admin/configuration/configuring-github-pages-on-your-appliance - /admin/configuration/configuring-github-pages-on-your-appliance - - /enterprise/admin/guides/installation/configuring-github-pages-for-your-enterprise/ + - /enterprise/admin/guides/installation/configuring-github-pages-for-your-enterprise - /admin/configuration/configuring-github-pages-for-your-enterprise versions: ghes: '*' diff --git a/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/configuring-time-synchronization.md b/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/configuring-time-synchronization.md index e5059a4bcae2..0d0af44dc001 100644 --- a/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/configuring-time-synchronization.md +++ b/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/configuring-time-synchronization.md @@ -1,11 +1,11 @@ --- -title: 時間の同期の設定 -intro: '{% data variables.product.prodname_ghe_server %} は、NTP サーバーに接続することによって自動的に時刻を同期させます。 時刻の同期に使われるNTPサーバは設定できます。あるいはデフォルトのNTPサーバを利用することもできます。' +title: Configuring time synchronization +intro: '{% data variables.product.prodname_ghe_server %} automatically synchronizes its clock by connecting to NTP servers. You can set the NTP servers that are used to synchronize the clock, or you can use the default NTP servers.' redirect_from: - - /enterprise/admin/articles/adjusting-the-clock/ - - /enterprise/admin/articles/configuring-time-zone-and-ntp-settings/ - - /enterprise/admin/articles/setting-ntp-servers/ - - /enterprise/admin/categories/time/ + - /enterprise/admin/articles/adjusting-the-clock + - /enterprise/admin/articles/configuring-time-zone-and-ntp-settings + - /enterprise/admin/articles/setting-ntp-servers + - /enterprise/admin/categories/time - /enterprise/admin/installation/configuring-time-synchronization - /enterprise/admin/configuration/configuring-time-synchronization - /admin/configuration/configuring-time-synchronization @@ -19,29 +19,31 @@ topics: - Networking shortTitle: Configure time settings --- - -## デフォルトのNTPサーバの変更 +## Changing the default NTP servers {% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} -2. 左のサイドバーで**Time（時間）**をクリックしてください。 ![{% data variables.enterprise.management_console %} サイドバーでの [Time] ボタン](/assets/images/enterprise/management-console/sidebar-time.png) -3. "Primary NTP server（プライマリのNTPサーバ）"の下で、プライマリNTPサーバのホスト名を入力してください。 "Secondary NTP server（セカンダリのNTPサーバ）"の下で、セカンダリのNTPサーバのホスト名を入力してください。 ![{% data variables.enterprise.management_console %} でのプライマリとセカンダリの NTP サーバーのためのフィールド](/assets/images/enterprise/management-console/ntp-servers.png) -4. ページの下部で **Save settings（設定の保存）**をクリックしてください。 ![{% data variables.enterprise.management_console %} での [Save settings] ボタン](/assets/images/enterprise/management-console/save-settings.png) -5. 設定が完了するのを待ってください。 +2. In the left sidebar, click **Time**. + ![The Time button in the {% data variables.enterprise.management_console %} sidebar](/assets/images/enterprise/management-console/sidebar-time.png) +3. Under "Primary NTP server," type the hostname of the primary NTP server. Under "Secondary NTP server," type the hostname of the secondary NTP server. + ![The fields for primary and secondary NTP servers in the {% data variables.enterprise.management_console %}](/assets/images/enterprise/management-console/ntp-servers.png) +4. At the bottom of the page, click **Save settings**. + ![The Save settings button in the {% data variables.enterprise.management_console %}](/assets/images/enterprise/management-console/save-settings.png) +5. Wait for the configuration run to complete. -## 大きな時間の乱れの修正 +## Correcting a large time drift -NTP プロトコルは小さな時間同期の不一致を継続的に修正します。 管理シェルを使用すれば、時間を直ちに同期させることができます。 +The NTP protocol continuously corrects small time synchronization discrepancies. You can use the administrative shell to synchronize time immediately. {% note %} -**ノート:** - - 協定世界時 (UTC) ゾーンは変更できません。 - - ハイパーバイザーが仮想マシンの時刻を設定しようとするのを回避しなければなりません。 詳しい情報については、仮想化プロバイダが提供しているドキュメンテーションを参照してください。 +**Notes:** + - You can't modify the Coordinated Universal Time (UTC) zone. + - You should prevent your hypervisor from trying to set the virtual machine's clock. For more information, see the documentation provided by the virtualization provider. {% endnote %} -- `chronyc` コマンドを使用して、サーバーを設定済みの NTP サーバーと同期させます。 例: +- Use the `chronyc` command to synchronize the server with the configured NTP server. For example: ```shell $ sudo chronyc -a makestep diff --git a/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/enabling-private-mode.md b/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/enabling-private-mode.md index 2d12b5589abc..a4343fa9a893 100644 --- a/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/enabling-private-mode.md +++ b/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/enabling-private-mode.md @@ -1,10 +1,10 @@ --- -title: プライベートモードの有効化 -intro: 'プライベートモードでは、{% data variables.product.prodname_ghe_server %} はインストールにアクセスするすべてのユーザーにサインインを求めます。' +title: Enabling private mode +intro: 'In private mode, {% data variables.product.prodname_ghe_server %} requires every user to sign in to access the installation.' redirect_from: - - /enterprise/admin/articles/private-mode/ - - /enterprise/admin/guides/installation/security/ - - /enterprise/admin/guides/installation/securing-your-instance/ + - /enterprise/admin/articles/private-mode + - /enterprise/admin/guides/installation/security + - /enterprise/admin/guides/installation/securing-your-instance - /enterprise/admin/installation/enabling-private-mode - /enterprise/admin/configuration/enabling-private-mode - /admin/configuration/enabling-private-mode @@ -21,15 +21,15 @@ topics: - Privacy - Security --- - -{% data variables.product.product_location %}がインターネット経由でパブリックにアクセス可能になっている場合、プライベートモードを有効化しなければなりません。 プライベートモードでは、ユーザは`git://`経由でリポジトリを匿名クローンすることはできません。 ビルトイン認証も有効化されている場合、新しいユーザがインスタンスにアカウントを作成するには管理者が招待しなければなりません。 詳しい情報については"[ビルトイン認証の利用](/enterprise/{{ currentVersion }}/admin/guides/user-management/using-built-in-authentication)"を参照してください。 +You must enable private mode if {% data variables.product.product_location %} is publicly accessible over the Internet. In private mode, users cannot anonymously clone repositories over `git://`. If built-in authentication is also enabled, an administrator must invite new users to create an account on the instance. For more information, see "[Using built-in authentication](/enterprise/{{ currentVersion }}/admin/guides/user-management/using-built-in-authentication)." {% data reusables.enterprise_installation.image-urls-viewable-warning %} -プライベートモードを有効にすると、認証されていない Git 操作 (および {% data variables.product.product_location %} へのネットワークアクセス権を所有する人) に、匿名 Git 読み取りアクセスを有効にしたインスタンスで、パブリックリポジトリのコードの読み取りを許可できます。 詳しい情報については[管理者にパブリックリポジトリの匿名Git読み取りアクセスの有効化を許可する](/enterprise/{{ currentVersion }}/admin/guides/user-management/allowing-admins-to-enable-anonymous-git-read-access-to-public-repositories)を参照してください。 +With private mode enabled, you can allow unauthenticated Git operations (and anyone with network access to {% data variables.product.product_location %}) to read a public repository's code on your instance with anonymous Git read access enabled. For more information, see "[Allowing admins to enable anonymous Git read access to public repositories](/enterprise/{{ currentVersion }}/admin/guides/user-management/allowing-admins-to-enable-anonymous-git-read-access-to-public-repositories)." {% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} {% data reusables.enterprise_management_console.privacy %} -4. **Private mode（プライベートモード）**を選択してください。 ![プライベートモードを有効にするためのチェックボックス](/assets/images/enterprise/management-console/private-mode-checkbox.png) +4. Select **Private mode**. + ![Checkbox for enabling private mode](/assets/images/enterprise/management-console/private-mode-checkbox.png) {% data reusables.enterprise_management_console.save-settings %} diff --git a/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/site-admin-dashboard.md b/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/site-admin-dashboard.md index 610a1878cc8c..36e474e3e267 100644 --- a/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/site-admin-dashboard.md +++ b/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/site-admin-dashboard.md @@ -2,7 +2,7 @@ title: Site admin dashboard intro: '{% data reusables.enterprise_site_admin_settings.about-the-site-admin-dashboard %}' redirect_from: - - /enterprise/admin/articles/site-admin-dashboard/ + - /enterprise/admin/articles/site-admin-dashboard - /enterprise/admin/installation/site-admin-dashboard - /enterprise/admin/configuration/site-admin-dashboard - /admin/configuration/site-admin-dashboard diff --git a/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/troubleshooting-ssl-errors.md b/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/troubleshooting-ssl-errors.md index 160da3428844..40a22785f712 100644 --- a/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/troubleshooting-ssl-errors.md +++ b/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/troubleshooting-ssl-errors.md @@ -1,9 +1,9 @@ --- -title: SSLのエラーのトラブルシューティング -intro: アプライアンスでSSLの問題が生じたなら、解決のためのアクションを取ってください。 +title: Troubleshooting SSL errors +intro: 'If you run into SSL issues with your appliance, you can take actions to resolve them.' redirect_from: - - /enterprise/admin/articles/troubleshooting-ssl-errors/ - - /enterprise/admin/categories/dns-ssl-and-subdomain-configuration/ + - /enterprise/admin/articles/troubleshooting-ssl-errors + - /enterprise/admin/categories/dns-ssl-and-subdomain-configuration - /enterprise/admin/installation/troubleshooting-ssl-errors - /enterprise/admin/configuration/troubleshooting-ssl-errors - /admin/configuration/troubleshooting-ssl-errors @@ -19,64 +19,63 @@ topics: - Troubleshooting shortTitle: Troubleshoot SSL errors --- +## Removing the passphrase from your key file -## 鍵ファイルからのパスフレーズの除去 +If you have a Linux machine with OpenSSL installed, you can remove your passphrase. -OpenSSLがインストールされたLinuxマシンを使うなら、パスフレーズを除去できます。 - -1. オリジナルの鍵ファイルの名前を変えてください。 +1. Rename your original key file. ```shell $ mv yourdomain.key yourdomain.key.orig ``` -2. パスフレーズなしで新しい鍵を生成してください。 +2. Generate a new key without a passphrase. ```shell $ openssl rsa -in yourdomain.key.orig -out yourdomain.key ``` -このコマンドを実行すると、鍵のパスフレーズを入力するようプロンプトが表示されます。 +You'll be prompted for the key's passphrase when you run this command. -OpenSSL に関する詳しい情報については、[OpenSSL のドキュメンテーション](https://www.openssl.org/docs/)を参照してください。 +For more information about OpenSSL, see [OpenSSL's documentation](https://www.openssl.org/docs/). -## SSL証明書あるいは鍵のPEMフォーマットへの変換 +## Converting your SSL certificate or key into PEM format -OpenSSL をインストールしている場合、`openssl` コマンドを使って鍵を PEM フォーマットに変換できます。 たとえば鍵を DER フォーマットから PEM フォーマットに変換できます。 +If you have OpenSSL installed, you can convert your key into PEM format by using the `openssl` command. For example, you can convert a key from DER format into PEM format. ```shell $ openssl rsa -in yourdomain.der -inform DER -out yourdomain.key -outform PEM ``` -あるいは SSL Converter ツールを使って証明書を PEM フォーマットに変換することもできます。 詳しい情報については [SSL Converter ツールのドキュメンテーション](https://www.sslshopper.com/ssl-converter.html)を参照してください。 +Otherwise, you can use the SSL Converter tool to convert your certificate into the PEM format. For more information, see the [SSL Converter tool's documentation](https://www.sslshopper.com/ssl-converter.html). -## 鍵のアップロード後の反応のない環境 +## Unresponsive installation after uploading a key -SSL 鍵のアップロード後に {% data variables.product.product_location %} の反応がない場合、SSL 証明書のコピーを含む詳細事項と合わせて [{% data variables.product.prodname_enterprise %} Support に連絡](https://enterprise.github.com/support)してください。 +If {% data variables.product.product_location %} is unresponsive after uploading an SSL key, please [contact {% data variables.product.prodname_enterprise %} Support](https://enterprise.github.com/support) with specific details, including a copy of your SSL certificate. -## 証明書の検証エラー +## Certificate validity errors -Web ブラウザやコマンドラインの Git などのクライアントは、SSL 証明書の正当性が検証できなければエラーメッセージを表示します。 これはしばしば自己署名証明書の場合や、クライアントが認識しない中間ルート証明書から発行された "チェーンドルート" 証明書の場合に生じます。 +Clients such as web browsers and command-line Git will display an error message if they cannot verify the validity of an SSL certificate. This often occurs with self-signed certificates as well as "chained root" certificates issued from an intermediate root certificate that is not recognized by the client. -証明書認証局 (CA) によって署名された証明書を使っている場合は、{% data variables.product.prodname_ghe_server %} にアップロードする証明書ファイルには CA のルート証明を持つ証明書チェーンが含まれていなければなりません。 そのようなファイルを作成するには、証明書チェーン全体 (「証明書バンドル」とも呼ばれます) を証明書の終わりにつなげ、プリンシパル証明書の先頭にホスト名が来るようにしてください。 ほとんどのシステムでは、以下のようなコマンドでこの処理を行えます: +If you are using a certificate signed by a certificate authority (CA), the certificate file that you upload to {% data variables.product.prodname_ghe_server %} must include a certificate chain with that CA's root certificate. To create such a file, concatenate your entire certificate chain (or "certificate bundle") onto the end of your certificate, ensuring that the principal certificate with your hostname comes first. On most systems you can do this with a command similar to: ```shell $ cat yourdomain.com.crt bundle-certificates.crt > yourdomain.combined.crt ``` -証明書バンドル (たとえば `bundle-certificates.crt`) は、証明書認証局もしくは SSL のベンダーからダウンロードできるはずです。 +You should be able to download a certificate bundle (for example, `bundle-certificates.crt`) from your certificate authority or SSL vendor. -## 自己署名もしくは信頼されない証明書認証者（CA）ルート証明書のインストール +## Installing self-signed or untrusted certificate authority (CA) root certificates -{% data variables.product.prodname_ghe_server %} アプライアンスが、自己署名もしくは信頼されない証明書を使うネットワーク上の他のマシンとやりとりするのであれば、それらのシステムに HTTPS でアクセスできるようにするために、署名をした CA のルート証明書をシステム全体の証明書ストアにインポートしなければなりません。 +If your {% data variables.product.prodname_ghe_server %} appliance interacts with other machines on your network that use a self-signed or untrusted certificate, you will need to import the signing CA's root certificate into the system-wide certificate store in order to access those systems over HTTPS. -1. CA のルート証明書をローカルの証明書認証局から取得し、それが PEM フォーマットになっていることを確認してください。 -2. そのファイルを {% data variables.product.prodname_ghe_server %} アプライアンスにポート 122 の SSH 経由で "admin" ユーザとしてコピーしてください。 +1. Obtain the CA's root certificate from your local certificate authority and ensure it is in PEM format. +2. Copy the file to your {% data variables.product.prodname_ghe_server %} appliance over SSH as the "admin" user on port 122. ```shell $ scp -P 122 rootCA.crt admin@HOSTNAME:/home/admin ``` -3. {% data variables.product.prodname_ghe_server %} の管理シェルにポート 122 の SSH 経由で "admin" ユーザとして接続します。 +3. Connect to the {% data variables.product.prodname_ghe_server %} administrative shell over SSH as the "admin" user on port 122. ```shell $ ssh -p 122 admin@HOSTNAME ``` -4. 証明書をシステム全体の証明書ストアにインポートします。 +4. Import the certificate into the system-wide certificate store. ```shell $ ghe-ssl-ca-certificate-install -c rootCA.crt ``` diff --git a/translations/ja-JP/content/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud.md b/translations/ja-JP/content/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud.md index 5a1202b892df..27df363d25dd 100644 --- a/translations/ja-JP/content/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud.md +++ b/translations/ja-JP/content/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud.md @@ -3,9 +3,9 @@ title: Connecting your enterprise account to GitHub Enterprise Cloud shortTitle: Connect enterprise accounts intro: 'After you enable {% data variables.product.prodname_github_connect %}, you can share specific features and workflows between {% data variables.product.product_location %} and {% data variables.product.prodname_ghe_cloud %}.' redirect_from: - - /enterprise/admin/guides/developer-workflow/connecting-github-enterprise-to-github-com/ + - /enterprise/admin/guides/developer-workflow/connecting-github-enterprise-to-github-com - /enterprise/admin/guides/developer-workflow/connecting-github-enterprise-server-to-github-com - - /enterprise/admin/developer-workflow/connecting-github-enterprise-server-to-githubcom/ + - /enterprise/admin/developer-workflow/connecting-github-enterprise-server-to-githubcom - /enterprise/admin/installation/connecting-github-enterprise-server-to-github-enterprise-cloud - /enterprise/admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud - /admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud diff --git a/translations/ja-JP/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-the-dependency-graph-and-dependabot-alerts-on-your-enterprise-account.md b/translations/ja-JP/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-the-dependency-graph-and-dependabot-alerts-on-your-enterprise-account.md index 2691561e8b10..cc41266506e8 100644 --- a/translations/ja-JP/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-the-dependency-graph-and-dependabot-alerts-on-your-enterprise-account.md +++ b/translations/ja-JP/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-the-dependency-graph-and-dependabot-alerts-on-your-enterprise-account.md @@ -70,19 +70,23 @@ You can enable the dependency graph via the {% data variables.enterprise.managem {% endif %} {% data reusables.enterprise_site_admin_settings.sign-in %} 1. In the administrative shell, enable the dependency graph on {% data variables.product.product_location %}: - ``` shell - $ {% ifversion ghes > 3.1 %}ghe-config app.dependency-graph.enabled true{% else %}ghe-config app.github.dependency-graph-enabled true{% endif %} + {% ifversion ghes > 3.1 %}```shell + ghe-config app.dependency-graph.enabled true ``` + {% else %}```shell + ghe-config app.github.dependency-graph-enabled true + ghe-config app.github.vulnerability-alerting-and-settings-enabled true + ```{% endif %} {% note %} **Note**: For more information about enabling access to the administrative shell via SSH, see "[Accessing the administrative shell (SSH)](/enterprise/{{ currentVersion }}/admin/configuration/accessing-the-administrative-shell-ssh)." {% endnote %} -1. Apply the configuration. +2. Apply the configuration. ```shell $ ghe-config-apply ``` -1. Return to {% data variables.product.prodname_ghe_server %}. +3. Return to {% data variables.product.prodname_ghe_server %}. {% endif %} ### Enabling {% data variables.product.prodname_dependabot_alerts %} diff --git a/translations/ja-JP/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-contributions-between-your-enterprise-account-and-githubcom.md b/translations/ja-JP/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-contributions-between-your-enterprise-account-and-githubcom.md index 22ccd67d2eaa..dd4e7113c332 100644 --- a/translations/ja-JP/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-contributions-between-your-enterprise-account-and-githubcom.md +++ b/translations/ja-JP/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-contributions-between-your-enterprise-account-and-githubcom.md @@ -3,9 +3,9 @@ title: Enabling unified contributions between your enterprise account and GitHub shortTitle: Enable unified contributions intro: 'After enabling {% data variables.product.prodname_github_connect %}, you can allow {% data variables.product.prodname_ghe_cloud %} members to highlight their work on {% data variables.product.product_name %} by sending the contribution counts to their {% data variables.product.prodname_dotcom_the_website %} profiles.' redirect_from: - - /enterprise/admin/guides/developer-workflow/enabling-unified-contributions-between-github-enterprise-and-github-com/ - - /enterprise/admin/guides/developer-workflow/enabling-unified-contributions-between-github-enterprise-server-and-github-com/ - - /enterprise/admin/developer-workflow/enabling-unified-contributions-between-github-enterprise-server-and-githubcom/ + - /enterprise/admin/guides/developer-workflow/enabling-unified-contributions-between-github-enterprise-and-github-com + - /enterprise/admin/guides/developer-workflow/enabling-unified-contributions-between-github-enterprise-server-and-github-com + - /enterprise/admin/developer-workflow/enabling-unified-contributions-between-github-enterprise-server-and-githubcom - /enterprise/admin/installation/enabling-unified-contributions-between-github-enterprise-server-and-githubcom - /enterprise/admin/configuration/enabling-unified-contributions-between-github-enterprise-server-and-githubcom - /admin/configuration/enabling-unified-contributions-between-github-enterprise-server-and-githubcom diff --git a/translations/ja-JP/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-search-between-your-enterprise-account-and-githubcom.md b/translations/ja-JP/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-search-between-your-enterprise-account-and-githubcom.md index e857470482f0..023533717837 100644 --- a/translations/ja-JP/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-search-between-your-enterprise-account-and-githubcom.md +++ b/translations/ja-JP/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-search-between-your-enterprise-account-and-githubcom.md @@ -3,9 +3,9 @@ title: Enabling unified search between your enterprise account and GitHub.com shortTitle: Enable unified search intro: 'After enabling {% data variables.product.prodname_github_connect %}, you can allow search of {% data variables.product.prodname_dotcom_the_website %} for members of your enterprise on {% data variables.product.product_name %}.' redirect_from: - - /enterprise/admin/guides/developer-workflow/enabling-unified-search-between-github-enterprise-and-github-com/ - - /enterprise/admin/guides/developer-workflow/enabling-unified-search-between-github-enterprise-server-and-github-com/ - - /enterprise/admin/developer-workflow/enabling-unified-search-between-github-enterprise-server-and-githubcom/ + - /enterprise/admin/guides/developer-workflow/enabling-unified-search-between-github-enterprise-and-github-com + - /enterprise/admin/guides/developer-workflow/enabling-unified-search-between-github-enterprise-server-and-github-com + - /enterprise/admin/developer-workflow/enabling-unified-search-between-github-enterprise-server-and-githubcom - /enterprise/admin/installation/enabling-unified-search-between-github-enterprise-server-and-githubcom - /enterprise/admin/configuration/enabling-unified-search-between-github-enterprise-server-and-githubcom - /admin/configuration/enabling-unified-search-between-github-enterprise-server-and-githubcom diff --git a/translations/ja-JP/content/admin/configuration/managing-connections-between-your-enterprise-accounts/index.md b/translations/ja-JP/content/admin/configuration/managing-connections-between-your-enterprise-accounts/index.md index c5a822c47af6..f46553f05981 100644 --- a/translations/ja-JP/content/admin/configuration/managing-connections-between-your-enterprise-accounts/index.md +++ b/translations/ja-JP/content/admin/configuration/managing-connections-between-your-enterprise-accounts/index.md @@ -3,9 +3,9 @@ title: Managing connections between your enterprise accounts intro: 'With {% data variables.product.prodname_github_connect %}, you can share certain features and data between {% data variables.product.product_location %} and your {% data variables.product.prodname_ghe_cloud %} organization or enterprise account on {% data variables.product.prodname_dotcom_the_website %}.' redirect_from: - /enterprise/admin/developer-workflow/connecting-github-enterprise-to-github-com - - /enterprise/admin/guides/developer-workflow/connecting-github-enterprise-and-github-com/ - - /enterprise/admin/guides/developer-workflow/connecting-github-enterprise-server-and-github-com/ - - /enterprise/admin/developer-workflow/connecting-github-enterprise-server-and-githubcom/ + - /enterprise/admin/guides/developer-workflow/connecting-github-enterprise-and-github-com + - /enterprise/admin/guides/developer-workflow/connecting-github-enterprise-server-and-github-com + - /enterprise/admin/developer-workflow/connecting-github-enterprise-server-and-githubcom - /enterprise/admin/installation/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud - /enterprise/admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud - /admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud diff --git a/translations/ja-JP/content/admin/user-management/index.md b/translations/ja-JP/content/admin/user-management/index.md index 125066d5c777..5e5f8682b236 100644 --- a/translations/ja-JP/content/admin/user-management/index.md +++ b/translations/ja-JP/content/admin/user-management/index.md @@ -1,9 +1,9 @@ --- -title: ユーザ、Organization、リポジトリデータを管理する -shortTitle: ユーザ、Organization、リポジトリデータを管理する -intro: このガイドでは、Enterprise にサインインするユーザの認証方式、リポジトリへのアクセスとコラボレーションのための Organization と Team を作成する方法、およびユーザセキュリティで推奨されるベストプラクティスについて説明します。 +title: 'Managing users, organizations, and repositories' +shortTitle: 'Managing users, organizations, and repositories' +intro: 'This guide describes authentication methods for users signing in to your enterprise, how to create organizations and teams for repository access and collaboration, and suggested best practices for user security.' redirect_from: - - /enterprise/admin/categories/user-management/ + - /enterprise/admin/categories/user-management - /enterprise/admin/developer-workflow/using-webhooks-for-continuous-integration - /enterprise/admin/migrations - /enterprise/admin/clustering diff --git a/translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/adding-people-to-teams.md b/translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/adding-people-to-teams.md index 56c00d03b5ea..f02cedf91120 100644 --- a/translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/adding-people-to-teams.md +++ b/translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/adding-people-to-teams.md @@ -1,12 +1,12 @@ --- -title: Teamへの人の追加 +title: Adding people to teams redirect_from: - - /enterprise/admin/articles/adding-teams/ - - /enterprise/admin/articles/adding-or-inviting-people-to-teams/ - - /enterprise/admin/guides/user-management/adding-or-inviting-people-to-teams/ + - /enterprise/admin/articles/adding-teams + - /enterprise/admin/articles/adding-or-inviting-people-to-teams + - /enterprise/admin/guides/user-management/adding-or-inviting-people-to-teams - /enterprise/admin/user-management/adding-people-to-teams - /admin/user-management/adding-people-to-teams -intro: 'Team が作成されると、Organization の管理者はユーザを {% data variables.product.product_location %} から Team に追加し、どのリポジトリにアクセスできるようにするかを決定できます。' +intro: 'Once a team has been created, organization admins can add users from {% data variables.product.product_location %} to the team and determine which repositories they have access to.' versions: ghes: '*' type: how_to @@ -16,13 +16,12 @@ topics: - Teams - User account --- +Each team has its own individually defined [access permissions for repositories owned by your organization](/articles/permission-levels-for-an-organization). -各Teamには、それぞれに定義された[Organizatinが所有するリポジトリへのアクセス権限](/articles/permission-levels-for-an-organization)があります。 +- Members with the owner role can add or remove existing organization members from all teams. +- Members of teams that give admin permissions can only modify team membership and repositories for that team. -- オーナー権限を持つメンバーは、すべてのTeamから既存のOrganizationのメンバーを追加したり削除したりできます。 -- 管理者権限を与えるTeamのメンバーは、TeamのメンバーシップとそのTeamのリポジトリだけを変更できます。 - -## チームのセットアップ +## Setting up a team {% data reusables.profile.access_org %} {% data reusables.user_settings.access_org %} @@ -30,8 +29,8 @@ topics: {% data reusables.organizations.invite_to_team %} {% data reusables.organizations.review-team-repository-access %} -## TeamのLDAPグループへのマッピング（たとえばLDAP Syncをユーザ認証に使って） +## Mapping teams to LDAP groups (for instances using LDAP Sync for user authentication) {% data reusables.enterprise_management_console.badge_indicator %} -LDAPグループに同期されているTeamに新しいメンバーを追加するには、そのユーザをLDAPグループのメンバーとして追加するか、LDAPの管理者に連絡してください。 +To add a new member to a team synced to an LDAP group, add the user as a member of the LDAP group, or contact your LDAP administrator. diff --git a/translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/index.md b/translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/index.md index 11ee5f9dd3ff..9df1581688a7 100644 --- a/translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/index.md +++ b/translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/index.md @@ -1,8 +1,8 @@ --- title: Managing organizations in your enterprise redirect_from: - - /enterprise/admin/articles/adding-users-and-teams/ - - /enterprise/admin/categories/admin-bootcamp/ + - /enterprise/admin/articles/adding-users-and-teams + - /enterprise/admin/categories/admin-bootcamp - /enterprise/admin/user-management/organizations-and-teams - /enterprise/admin/user-management/managing-organizations-in-your-enterprise - /articles/managing-organizations-in-your-enterprise-account diff --git a/translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/managing-projects-using-jira.md b/translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/managing-projects-using-jira.md index ac33aeed84ce..10a117009a68 100644 --- a/translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/managing-projects-using-jira.md +++ b/translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/managing-projects-using-jira.md @@ -2,8 +2,8 @@ title: Managing projects using Jira intro: 'You can integrate Jira with {% data variables.product.prodname_enterprise %} for project management.' redirect_from: - - /enterprise/admin/guides/installation/project-management-using-jira/ - - /enterprise/admin/articles/project-management-using-jira/ + - /enterprise/admin/guides/installation/project-management-using-jira + - /enterprise/admin/articles/project-management-using-jira - /enterprise/admin/developer-workflow/managing-projects-using-jira - /enterprise/admin/developer-workflow/customizing-your-instance-with-integrations - /enterprise/admin/user-management/managing-projects-using-jira @@ -16,10 +16,9 @@ topics: - Project management shortTitle: Project management with Jira --- - ## Connecting Jira to a {% data variables.product.prodname_enterprise %} organization -1. http[s]://[hostname]/login で {% data variables.product.prodname_enterprise %}のアカウントにサインインする。 If already signed in, click on the {% data variables.product.prodname_dotcom %} logo in the top left corner. +1. Sign into your {% data variables.product.prodname_enterprise %} account at http[s]://[hostname]/login. If already signed in, click on the {% data variables.product.prodname_dotcom %} logo in the top left corner. 2. Click on your profile icon under the {% data variables.product.prodname_dotcom %} logo and select the organization you would like to connect with Jira. ![Select an organization](/assets/images/enterprise/orgs-and-teams/profile-select-organization.png) @@ -36,12 +35,12 @@ shortTitle: Project management with Jira ![Register new application button](/assets/images/enterprise/orgs-and-teams/register-oauth-application-button.png) -6. アプリケーションの設定を次のように記入する。 +6. Fill in the application settings: - In the **Application name** field, type "Jira" or any name you would like to use to identify the Jira instance. - In the **Homepage URL** field, type the full URL of your Jira instance. - In the **Authorization callback URL** field, type the full URL of your Jira instance. -7. **Register application** をクリックする。 -8. ページの上部の [**Client ID**] と [**Client Secret**] をメモしてください。 You will need these for configuring your Jira instance. +7. Click **Register application**. +8. At the top of the page, note the **Client ID** and **Client Secret**. You will need these for configuring your Jira instance. ## Jira instance configuration @@ -58,13 +57,13 @@ shortTitle: Project management with Jira ![Link GitHub account to Jira](/assets/images/enterprise/orgs-and-teams/jira/jira-link-github-account.png) -5. [**Add New Account**] (新規アカウントを追加) モーダルで、{% data variables.product.prodname_enterprise %} の設定を記入してください。 +5. In the **Add New Account** modal, fill in your {% data variables.product.prodname_enterprise %} settings: - From the **Host** dropdown menu, choose **{% data variables.product.prodname_enterprise %}**. - - **Team or User Account** の欄には、{% data variables.product.prodname_enterprise %}のOrganization、または個人アカウントの名前を入力する。 - - **OAuth Key** の欄には、{% data variables.product.prodname_enterprise %}のディベロッパーアプリケーションのClient ID を入力する。 - - **OAuth Secret** の欄には、{% data variables.product.prodname_enterprise %}のデベロッパーアプリケーションの Client Secret を入力する。 + - In the **Team or User Account** field, type the name of your {% data variables.product.prodname_enterprise %} organization or personal account. + - In the **OAuth Key** field, type the Client ID of your {% data variables.product.prodname_enterprise %} developer application. + - In the **OAuth Secret** field, type the Client Secret for your {% data variables.product.prodname_enterprise %} developer application. - If you don't want to link new repositories owned by your {% data variables.product.prodname_enterprise %} organization or personal account, deselect **Auto Link New Repositories**. - If you don't want to enable smart commits, deselect **Enable Smart Commits**. - - [**Add**] をクリックします。 -6. {% data variables.product.prodname_enterprise %}に対して与えるアクセス権を確認して、**Authorize application** をクリックする。 -7. 必要であれば、パスワードを入力する。 + - Click **Add**. +6. Review the permissions you are granting to your {% data variables.product.prodname_enterprise %} account and click **Authorize application**. +7. If necessary, type your password to continue. diff --git a/translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/preventing-users-from-creating-organizations.md b/translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/preventing-users-from-creating-organizations.md index 05d4f1301f4c..41cbf9b46b0f 100644 --- a/translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/preventing-users-from-creating-organizations.md +++ b/translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/preventing-users-from-creating-organizations.md @@ -1,11 +1,11 @@ --- -title: ユーザによるOrganizationの作成の禁止 +title: Preventing users from creating organizations redirect_from: - - /enterprise/admin/articles/preventing-users-from-creating-organizations/ - - /enterprise/admin/hidden/preventing-users-from-creating-organizations/ + - /enterprise/admin/articles/preventing-users-from-creating-organizations + - /enterprise/admin/hidden/preventing-users-from-creating-organizations - /enterprise/admin/user-management/preventing-users-from-creating-organizations - /admin/user-management/preventing-users-from-creating-organizations -intro: ユーザが Enterprise 内に Organization を作成できないようにすることができます。 +intro: You can prevent users from creating organizations in your enterprise. versions: ghes: '*' ghae: '*' @@ -16,7 +16,6 @@ topics: - Policies shortTitle: Prevent organization creation --- - {% data reusables.enterprise-accounts.access-enterprise %} {% ifversion ghes or ghae %} {% data reusables.enterprise-accounts.policies-tab %} @@ -24,4 +23,5 @@ shortTitle: Prevent organization creation {% data reusables.enterprise-accounts.settings-tab %} {% endif %} {% data reusables.enterprise-accounts.options-tab %} -4. [Users can create organizations（ユーザによるOrganizationの作成可能）] の下で、ドロップダウンメニューを使って [**Enabled（有効化）**] あるいは [**Disabled（無効化）**] を選択してください。 ![[Users can create organizations] ドロップダウン](/assets/images/enterprise/site-admin-settings/users-create-orgs-dropdown.png) +4. Under "Users can create organizations", use the drop-down menu and click **Enabled** or **Disabled**. +![Users can create organizations drop-down](/assets/images/enterprise/site-admin-settings/users-create-orgs-dropdown.png) diff --git a/translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/viewing-the-audit-logs-for-organizations-in-your-enterprise.md b/translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/viewing-the-audit-logs-for-organizations-in-your-enterprise.md index 373f4381fc34..8ee2d906ece8 100644 --- a/translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/viewing-the-audit-logs-for-organizations-in-your-enterprise.md +++ b/translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/viewing-the-audit-logs-for-organizations-in-your-enterprise.md @@ -4,7 +4,7 @@ intro: Enterprise owners can view aggregated actions from all of the organizatio product: '{% data reusables.gated-features.enterprise-accounts %}' redirect_from: - /github/setting-up-and-managing-your-enterprise/managing-organizations-in-your-enterprise-account/viewing-the-audit-logs-for-organizations-in-your-enterprise-account - - /articles/viewing-the-audit-logs-for-organizations-in-your-business-account/ + - /articles/viewing-the-audit-logs-for-organizations-in-your-business-account - /articles/viewing-the-audit-logs-for-organizations-in-your-enterprise-account - /github/setting-up-and-managing-your-enterprise-account/viewing-the-audit-logs-for-organizations-in-your-enterprise-account - /github/setting-up-and-managing-your-enterprise/viewing-the-audit-logs-for-organizations-in-your-enterprise-account diff --git a/translations/ja-JP/content/admin/user-management/managing-repositories-in-your-enterprise/configuring-git-large-file-storage-for-your-enterprise.md b/translations/ja-JP/content/admin/user-management/managing-repositories-in-your-enterprise/configuring-git-large-file-storage-for-your-enterprise.md index ff100011d438..96c09af59419 100644 --- a/translations/ja-JP/content/admin/user-management/managing-repositories-in-your-enterprise/configuring-git-large-file-storage-for-your-enterprise.md +++ b/translations/ja-JP/content/admin/user-management/managing-repositories-in-your-enterprise/configuring-git-large-file-storage-for-your-enterprise.md @@ -2,15 +2,15 @@ title: Configuring Git Large File Storage for your enterprise intro: '{% data reusables.enterprise_site_admin_settings.configuring-large-file-storage-short-description %}' redirect_from: - - /enterprise/admin/guides/installation/configuring-git-large-file-storage-on-github-enterprise/ + - /enterprise/admin/guides/installation/configuring-git-large-file-storage-on-github-enterprise - /enterprise/admin/installation/configuring-git-large-file-storage-on-github-enterprise-server - /enterprise/admin/installation/configuring-git-large-file-storage - /enterprise/admin/installation/configuring-git-large-file-storage-to-use-a-third-party-server - /enterprise/admin/installation/migrating-to-a-different-git-large-file-storage-server - - /enterprise/admin/articles/configuring-git-large-file-storage-for-a-repository/ - - /enterprise/admin/articles/configuring-git-large-file-storage-for-every-repository-owned-by-a-user-account-or-organization/ - - /enterprise/admin/articles/configuring-git-large-file-storage-for-your-appliance/ - - /enterprise/admin/guides/installation/migrating-to-different-large-file-storage-server/ + - /enterprise/admin/articles/configuring-git-large-file-storage-for-a-repository + - /enterprise/admin/articles/configuring-git-large-file-storage-for-every-repository-owned-by-a-user-account-or-organization + - /enterprise/admin/articles/configuring-git-large-file-storage-for-your-appliance + - /enterprise/admin/guides/installation/migrating-to-different-large-file-storage-server - /enterprise/admin/user-management/configuring-git-large-file-storage-for-your-enterprise - /admin/user-management/configuring-git-large-file-storage-for-your-enterprise versions: diff --git a/translations/ja-JP/content/admin/user-management/managing-repositories-in-your-enterprise/disabling-git-ssh-access-on-your-enterprise.md b/translations/ja-JP/content/admin/user-management/managing-repositories-in-your-enterprise/disabling-git-ssh-access-on-your-enterprise.md index 93361d35777c..e02538d16aef 100644 --- a/translations/ja-JP/content/admin/user-management/managing-repositories-in-your-enterprise/disabling-git-ssh-access-on-your-enterprise.md +++ b/translations/ja-JP/content/admin/user-management/managing-repositories-in-your-enterprise/disabling-git-ssh-access-on-your-enterprise.md @@ -1,20 +1,20 @@ --- -title: Enterprise で Git SSH アクセスを無効化する +title: Disabling Git SSH access on your enterprise redirect_from: - - /enterprise/admin/hidden/disabling-ssh-access-for-a-user-account/ - - /enterprise/admin/articles/disabling-ssh-access-for-a-user-account/ - - /enterprise/admin/hidden/disabling-ssh-access-for-your-appliance/ - - /enterprise/admin/articles/disabling-ssh-access-for-your-appliance/ - - /enterprise/admin/hidden/disabling-ssh-access-for-an-organization/ - - /enterprise/admin/articles/disabling-ssh-access-for-an-organization/ - - /enterprise/admin/hidden/disabling-ssh-access-to-a-repository/ - - /enterprise/admin/articles/disabling-ssh-access-to-a-repository/ - - /enterprise/admin/guides/installation/disabling-git-ssh-access-on-github-enterprise/ + - /enterprise/admin/hidden/disabling-ssh-access-for-a-user-account + - /enterprise/admin/articles/disabling-ssh-access-for-a-user-account + - /enterprise/admin/hidden/disabling-ssh-access-for-your-appliance + - /enterprise/admin/articles/disabling-ssh-access-for-your-appliance + - /enterprise/admin/hidden/disabling-ssh-access-for-an-organization + - /enterprise/admin/articles/disabling-ssh-access-for-an-organization + - /enterprise/admin/hidden/disabling-ssh-access-to-a-repository + - /enterprise/admin/articles/disabling-ssh-access-to-a-repository + - /enterprise/admin/guides/installation/disabling-git-ssh-access-on-github-enterprise - /enterprise/admin/installation/disabling-git-ssh-access-on-github-enterprise-server - /enterprise/admin/user-management/disabling-git-ssh-access-on-github-enterprise-server - /admin/user-management/disabling-git-ssh-access-on-github-enterprise-server - /admin/user-management/disabling-git-ssh-access-on-your-enterprise -intro: Enterprise 内の特定のリポジトリまたはすべてのリポジトリで、ユーザが SSH 経由で Git を使用できないようにすることができます。 +intro: You can prevent people from using Git over SSH for certain or all repositories on your enterprise. versions: ghes: '*' ghae: '*' @@ -26,8 +26,7 @@ topics: - SSH shortTitle: Disable SSH for Git --- - -## 特定のリポジトリへのGit SSHアクセスの無効化 +## Disabling Git SSH access to a specific repository {% data reusables.enterprise_site_admin_settings.override-policy %} @@ -37,9 +36,10 @@ shortTitle: Disable SSH for Git {% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.admin-top-tab %} {% data reusables.enterprise_site_admin_settings.admin-tab %} -1. [Git SSH access] で、ドロップダウンメニューを使用して [**Disabled**] を選択します。 ![無効化オプションが選択されたGit SSHアクセスドロップダウンメニュー](/assets/images/enterprise/site-admin-settings/git-ssh-access-repository-setting.png) +1. Under "Git SSH access", use the drop-down menu, and click **Disabled**. + ![Git SSH access drop-down menu with disabled option selected](/assets/images/enterprise/site-admin-settings/git-ssh-access-repository-setting.png) -## ユーザもしくは組織が所有するすべてのリポジトリへのGit SSHアクセスの無効化 +## Disabling Git SSH access to all repositories owned by a user or organization {% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.search-user-or-org %} @@ -47,9 +47,10 @@ shortTitle: Disable SSH for Git {% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.admin-top-tab %} {% data reusables.enterprise_site_admin_settings.admin-tab %} -7. [Git SSH access] で、ドロップダウンメニューを使用して [**Disabled**] を選択します。 続いて、**Enforce on all repositories（すべてのリポジトリで強制）**を選択してください。 ![無効化オプションが選択されたGit SSHアクセスドロップダウンメニュー](/assets/images/enterprise/site-admin-settings/git-ssh-access-organization-setting.png) +7. Under "Git SSH access", use the drop-down menu, and click **Disabled**. Then, select **Enforce on all repositories**. + ![Git SSH access drop-down menu with disabled option selected](/assets/images/enterprise/site-admin-settings/git-ssh-access-organization-setting.png) -## Enterprise 内のすべてのリポジトリへの Git SSH アクセスを無効化する +## Disabling Git SSH access to all repositories in your enterprise {% data reusables.enterprise-accounts.access-enterprise %} {% ifversion ghes or ghae %} @@ -58,4 +59,5 @@ shortTitle: Disable SSH for Git {% data reusables.enterprise-accounts.settings-tab %} {% endif %} {% data reusables.enterprise-accounts.options-tab %} -7. [Git SSH access] で、ドロップダウンメニューを使用して [**Disabled**] を選択します。 続いて、**Enforce on all repositories（すべてのリポジトリで強制）**を選択してください。 ![無効化オプションが選択されたGit SSHアクセスドロップダウンメニュー](/assets/images/enterprise/site-admin-settings/git-ssh-access-appliance-setting.png) +7. Under "Git SSH access", use the drop-down menu, and click **Disabled**. Then, select **Enforce on all repositories**. + ![Git SSH access drop-down menu with disabled option selected](/assets/images/enterprise/site-admin-settings/git-ssh-access-appliance-setting.png) diff --git a/translations/ja-JP/content/admin/user-management/managing-repositories-in-your-enterprise/troubleshooting-service-hooks.md b/translations/ja-JP/content/admin/user-management/managing-repositories-in-your-enterprise/troubleshooting-service-hooks.md index f322c84dcb73..90b442a4b8a2 100644 --- a/translations/ja-JP/content/admin/user-management/managing-repositories-in-your-enterprise/troubleshooting-service-hooks.md +++ b/translations/ja-JP/content/admin/user-management/managing-repositories-in-your-enterprise/troubleshooting-service-hooks.md @@ -1,8 +1,8 @@ --- -title: サービスフックのトラブルシューティング -intro: ペイロードが配信されない場合、以下の一般的な問題をチェックしてください。 +title: Troubleshooting service hooks +intro: 'If payloads aren''t being delivered, check for these common problems.' redirect_from: - - /enterprise/admin/articles/troubleshooting-service-hooks/ + - /enterprise/admin/articles/troubleshooting-service-hooks - /enterprise/admin/developer-workflow/troubleshooting-service-hooks - /enterprise/admin/user-management/troubleshooting-service-hooks - /admin/user-management/troubleshooting-service-hooks @@ -13,31 +13,36 @@ topics: - Enterprise shortTitle: Troubleshoot service hooks --- +## Getting information on deliveries -## デリバリーについての情報を入手 - -任意のリポジトリのすべてのサービスフックのデリバリに対する最後のレスポンスに関する情報を調べることができます。 +You can find information for the last response of all service hooks deliveries on any repository. {% data reusables.enterprise_site_admin_settings.access-settings %} -2. 調べるリポジトリを開ける。 -3. ナビゲーションサイドバーで **Hooks** のリンクをクリックする。 ![フックのサイドバー](/assets/images/enterprise/settings/Enterprise-Hooks-Sidebar.png) -4. 問題が発生しているサービスフックで、**Latest Delivery** へのリンクをクリックする。 ![フックの詳細](/assets/images/enterprise/settings/Enterprise-Hooks-Details.png) -5. [**Remote Calls**] (リモート呼び出し) の下に、リモートサーバーへの POST の際に使われたヘッダと、リモートサーバーがあなたの環境に返信したレスポンスを見ることができます。 +2. Browse to the repository you're investigating. +3. Click on the **Hooks** link in the navigation sidebar. + ![Hooks Sidebar](/assets/images/enterprise/settings/Enterprise-Hooks-Sidebar.png) +4. Click on the **Latest Delivery** link under the service hook having problems. + ![Hook Details](/assets/images/enterprise/settings/Enterprise-Hooks-Details.png) +5. Under **Remote Calls**, you'll see the headers that were used when POSTing to the remote server along with the response that the remote server sent back to your installation. -## ペイロードの表示 +## Viewing the payload {% data reusables.enterprise_site_admin_settings.access-settings %} -2. 調べるリポジトリを開ける。 -3. ナビゲーションサイドバーで **Hooks** のリンクをクリックする。 ![フックのサイドバー](/assets/images/enterprise/settings/Enterprise-Hooks-Sidebar.png) -4. 問題が発生しているサービスフックで、**Latest Delivery** へのリンクをクリックする。 -5. [**Delivery**] をクリックします。 ![ペイロードの表示](/assets/images/enterprise/settings/Enterprise-Hooks-Payload.png) +2. Browse to the repository you're investigating. +3. Click on the **Hooks** link in the navigation sidebar. + ![Hooks Sidebar](/assets/images/enterprise/settings/Enterprise-Hooks-Sidebar.png) +4. Click on the **Latest Delivery** link under the service hook having problems. +5. Click **Delivery**. + ![Viewing the payload](/assets/images/enterprise/settings/Enterprise-Hooks-Payload.png) -## 過去のデリバリーの表示 +## Viewing past deliveries -デリバリーは 15 日間保存されます。 +Deliveries are stored for 15 days. {% data reusables.enterprise_site_admin_settings.access-settings %} -2. 調べるリポジトリを開ける。 -3. ナビゲーションサイドバーで **Hooks** のリンクをクリックする。 ![フックのサイドバー](/assets/images/enterprise/settings/Enterprise-Hooks-Sidebar.png) -4. 問題が発生しているサービスフックで、**Latest Delivery** へのリンクをクリックする。 -5. その特定のフックに対する他のデリバリーを見るには、[**More for this Hook ID**] をクリックします。 ![デリバリーをさらに表示](/assets/images/enterprise/settings/Enterprise-Hooks-More-Deliveries.png) +2. Browse to the repository you're investigating. +3. Click on the **Hooks** link in the navigation sidebar. + ![Hooks Sidebar](/assets/images/enterprise/settings/Enterprise-Hooks-Sidebar.png) +4. Click on the **Latest Delivery** link under the service hook having problems. +5. To view other deliveries to that specific hook, click **More for this Hook ID**: + ![Viewing more deliveries](/assets/images/enterprise/settings/Enterprise-Hooks-More-Deliveries.png) diff --git a/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/auditing-ssh-keys.md b/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/auditing-ssh-keys.md index e900f4851ffc..b7fb055a4907 100644 --- a/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/auditing-ssh-keys.md +++ b/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/auditing-ssh-keys.md @@ -1,8 +1,8 @@ --- -title: SSHキーの監査 -intro: サイト管理者は SSH キーのインスタンス全体に対する監査を始めることができます。 +title: Auditing SSH keys +intro: Site administrators can initiate an instance-wide audit of SSH keys. redirect_from: - - /enterprise/admin/articles/auditing-ssh-keys/ + - /enterprise/admin/articles/auditing-ssh-keys - /enterprise/admin/user-management/auditing-ssh-keys - /admin/user-management/auditing-ssh-keys versions: @@ -15,52 +15,51 @@ topics: - Security - SSH --- +Once initiated, the audit disables all existing SSH keys and forces users to approve or reject them before they're able to clone, pull, or push to any repositories. An audit is useful in situations where an employee or contractor leaves the company and you need to ensure that all keys are verified. -監査が開始されると、現在の SSHキーがすべて無効となります。リポジトリのクローン、プル、プッシュといった操作をするためには、ユーザは SSH キーの承認または拒否をしなければなりません。 監査は、従業員の退職時や請負業者の撤収時など、すべてのキーを検証する必要があるときに役立ちます。 +## Initiating an audit -## 監査を開始する +You can initiate an SSH key audit from the "All users" tab of the site admin dashboard: -SSH キーの監査は、サイト管理ダッシュボードの [All users] タブから開始できます。 +![Starting a public key audit](/assets/images/enterprise/security/Enterprise-Start-Key-Audit.png) -![公開鍵の監査の開始](/assets/images/enterprise/security/Enterprise-Start-Key-Audit.png) +After you click the "Start public key audit" button, you'll be taken to a confirmation screen explaining what will happen next: -"Start public key audit（公開鍵の監査の開始）" のボタンをクリックしたら、その後の流れを説明する確認画面に移動します。 +![Confirming the audit](/assets/images/enterprise/security/Enterprise-Begin-Audit.png) -![監査の確認](/assets/images/enterprise/security/Enterprise-Begin-Audit.png) +After you click the "Begin audit" button, all SSH keys are invalidated and will require approval. You'll see a notification indicating the audit has begun. -\[Begin audit\] (監査を開始) ボタンをクリックすると、すべての SSH キーは無効となり、承認が必要になります。 監査が始まったことを示す通知が表示されます。 +## What users see -## ユーザに対する表示 - -ユーザがSSH経由で Git のオペレーションを実行した場合は、オペレーションが失敗し、次のメッセージが表示されます。 +If a user attempts to perform any git operation over SSH, it will fail and provide them with the following message: ```shell -ERROR: Hi ユーザ名. We're doing an SSH key audit. +ERROR: Hi username. We're doing an SSH key audit. Please visit http(s)://hostname/settings/ssh/audit/2 to approve this key so we know it's safe. Fingerprint: ed:21:60:64:c0:dc:2b:16:0f:54:5f:2b:35:2a:94:91 fatal: The remote end hung up unexpectedly ``` -ユーザがリンクをたどると、アカウントのキーを承認するよう要求されます。 +When they follow the link, they're asked to approve the keys on their account: -![キーの監査](/assets/images/enterprise/security/Enterprise-Audit-SSH-Keys.jpg) +![Auditing keys](/assets/images/enterprise/security/Enterprise-Audit-SSH-Keys.jpg) -キーを承認または拒否したら、今まで通りリポジトリを使えるようになります。 +After they approve or reject their keys, they'll be able interact with repositories as usual. -## SSH キーを追加する +## Adding an SSH key -新規ユーザは、SSHキーを追加する際にパスワードを要求されます。 +New users will be prompted for their password when adding an SSH key: -![パスワードの確認](/assets/images/help/settings/sudo_mode_popup.png) +![Password confirmation](/assets/images/help/settings/sudo_mode_popup.png) -ユーザがキーを追加したら、次のような通知メールが届きます。 +When a user adds a key, they'll receive a notification email that will look something like this: The following SSH key was added to your account: - + [title] ed:21:60:64:c0:dc:2b:16:0f:54:5f:2b:35:2a:94:91 - + If you believe this key was added in error, you can remove the key and disable access at the following location: - + http(s)://HOSTNAME/settings/ssh diff --git a/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/auditing-users-across-your-enterprise.md b/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/auditing-users-across-your-enterprise.md index 6450f05e2f78..b73c09ee997c 100644 --- a/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/auditing-users-across-your-enterprise.md +++ b/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/auditing-users-across-your-enterprise.md @@ -1,8 +1,8 @@ --- -title: Enterprise にわたるユーザの監査 +title: Auditing users across your enterprise intro: 'The audit log dashboard shows site administrators the actions performed by all users and organizations across your enterprise within the current month and previous six months. The audit log includes details such as who performed the action, what the action was, and when the action was performed.' redirect_from: - - /enterprise/admin/guides/user-management/auditing-users-across-an-organization/ + - /enterprise/admin/guides/user-management/auditing-users-across-an-organization - /enterprise/admin/user-management/auditing-users-across-your-instance - /admin/user-management/auditing-users-across-your-instance - /admin/user-management/auditing-users-across-your-enterprise @@ -18,103 +18,102 @@ topics: - User account shortTitle: Audit users --- +## Accessing the audit log -## Audit log にアクセスする +The audit log dashboard gives you a visual display of audit data across your enterprise. -Audit log ダッシュボードには、Enterprise 全体の監査データが表示されます。 - -![インスタンスにわたるAudit logのダッシュボード](/assets/images/enterprise/site-admin-settings/audit-log-dashboard-admin-center.png) +![Instance wide audit log dashboard](/assets/images/enterprise/site-admin-settings/audit-log-dashboard-admin-center.png) {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.audit-log-tab %} -地図内では、世界中のイベントを見るためにパンやズームができます。 国にカーソルを合わせれば、その国のイベントの簡単な集計が表示されます。 +Within the map, you can pan and zoom to see events around the world. Hover over a country to see a quick count of events from that country. -## Enterprise にわたるイベントの検索 +## Searching for events across your enterprise -Audit log には、Enterprise 内で行われたアクションに関する次の情報が一覧表示されます。 +The audit log lists the following information about actions made within your enterprise: -* アクションが行われた[リポジトリ](#search-based-on-the-repository) -* アクションを行った[ユーザ](#search-based-on-the-user) -* アクションに関係する[Organization](#search-based-on-the-organization) -* 行われた[アクション](#search-based-on-the-action-performed) -* アクションが行われた[国](#search-based-on-the-location) -* アクションが生じた[日時](#search-based-on-the-time-of-action) +* [The repository](#search-based-on-the-repository) an action was performed in +* [The user](#search-based-on-the-user) who performed the action +* [Which organization](#search-based-on-the-organization) an action pertained to +* [The action](#search-based-on-the-action-performed) that was performed +* [Which country](#search-based-on-the-location) the action took place in +* [The date and time](#search-based-on-the-time-of-action) the action occurred {% warning %} -**ノート:** +**Notes:** -- Audit logのエントリはテキストを使った検索はできませんが、様々なフィルタを使って検索クエリを構築できます。 {% data variables.product.product_name %} は、{% data variables.product.product_name %} 全体を検索するための多くの演算子をサポートしています。 詳細は「[{% data variables.product.prodname_dotcom %} での検索について](/github/searching-for-information-on-github/about-searching-on-github)」を参照してください。 +- While you can't use text to search for audit entries, you can construct search queries using a variety of filters. {% data variables.product.product_name %} supports many operators for searching across {% data variables.product.product_name %}. For more information, see "[About searching on {% data variables.product.prodname_dotcom %}](/github/searching-for-information-on-github/about-searching-on-github)." - Audit records are available for the current month and every day of the previous six months. {% endwarning %} -### リポジトリに基づく検索 +### Search based on the repository -`repo` 修飾子は、Organization が所有する特定のリポジトリにアクションを制限します。 例: +The `repo` qualifier limits actions to a specific repository owned by your organization. For example: -* `repo:my-org/our-repo`は`my-org` Organization内の`our-repo`リポジトリで起きたすべてのイベントを検索します。 -* `repo:my-org/our-repo repo:my-org/another-repo`は、`my-org` Organization内の`our-repo`及び`another-repo`の両リポジトリ内で起きたすべてのイベントを検索します。 -* `-repo:my-org/not-this-repo`は、`my-org` Organization内の`not-this-repo`リポジトリで起きたすべてのイベントを除外します。 +* `repo:my-org/our-repo` finds all events that occurred for the `our-repo` repository in the `my-org` organization. +* `repo:my-org/our-repo repo:my-org/another-repo` finds all events that occurred for both the `our-repo` and `another-repo` repositories in the `my-org` organization. +* `-repo:my-org/not-this-repo` excludes all events that occurred for the `not-this-repo` repository in the `my-org` organization. -`repo`修飾子内には、Organizationの名前を含めなければなりません。単に`repo:our-repo`として検索することはできません。 +You must include your organization's name within the `repo` qualifier; searching for just `repo:our-repo` will not work. -### ユーザーに基づく検索 +### Search based on the user -`actor` 修飾子は、アクションを実行した Organization のメンバーに基づいてイベントの範囲を設定します。 例: +The `actor` qualifier scopes events based on the member of your organization that performed the action. For example: -* `actor:octocat`は`octocat`が行ったすべてのイベントを検索します。 -* `actor:octocat actor:hubot`は、`octocat`及び`hubot`が行ったすべてのイベントを検索します。 -* `-actor:hubot`は、`hubot`が行ったすべてのイベントを除外します。 +* `actor:octocat` finds all events performed by `octocat`. +* `actor:octocat actor:hubot` finds all events performed by both `octocat` and `hubot`. +* `-actor:hubot` excludes all events performed by `hubot`. -使用できるのは {% data variables.product.product_name %} ユーザ名のみで、個人の本当の名前ではありません。 +You can only use a {% data variables.product.product_name %} username, not an individual's real name. -### Organizationに基づく検索 +### Search based on the organization -`org` 修飾子は、特定の Organization にアクションを限定します。 例: +The `org` qualifier limits actions to a specific organization. For example: -* `org:my-org` は `my-org` という Organization で生じたすべてのイベントを検索します。 -* `org:my-org action:team`は`my-org`というOrganization内で行われたすべてのteamイベントを検索します。 -* `-org:my-org` は `my-org` という Organization で生じたすべてのイベントを除外します。 +* `org:my-org` finds all events that occurred for the `my-org` organization. +* `org:my-org action:team` finds all team events performed within the `my-org` organization. +* `-org:my-org` excludes all events that occurred for the `my-org` organization. -### 実行されたアクションに基づく検索 +### Search based on the action performed -`action`修飾子は、特定のイベントをカテゴリ内でグループ化して検索します。 以下のカテゴリに関連するイベントの詳しい情報については「[監査済みのアクション](/admin/user-management/audited-actions)」を参照してください。 +The `action` qualifier searches for specific events, grouped within categories. For information on the events associated with these categories, see "[Audited actions](/admin/user-management/audited-actions)". -| カテゴリ名 | 説明 | -| ------ | -------------------------------------------- | -| `フック` | webhookに関連するすべてのアクティビティを含みます。 | -| `org` | Organizationのメンバーシップに関連するすべてのアクティビティを含みます。 | -| `repo` | Organizationが所有するリポジトリに関連するすべてのアクティビティを含みます。 | -| `Team` | Organization内のチームに関連するすべてのアクティビティを含みます。 | +| Category name | Description +|------------------|------------------- +| `hook` | Contains all activities related to webhooks. +| `org` | Contains all activities related organization membership +| `repo` | Contains all activities related to the repositories owned by your organization. +| `team` | Contains all activities related to teams in your organization. -次の用語を使用すれば、特定の一連の行動を検索できます。 例: +You can search for specific sets of actions using these terms. For example: -* `action:team`はteamカテゴリ内でグループ化されたすべてのイベントを検索します。 -* `-action:billing`はbillingカテゴリ内のすべてのイベントを除外します。 +* `action:team` finds all events grouped within the team category. +* `-action:billing` excludes all events in the billing category. -各カテゴリには、フィルタリングできる一連の関連イベントがあります。 例: +Each category has a set of associated events that you can filter on. For example: -* `action:team.create`はTeamが作成されたすべてのイベントを検索します。 -* `-action:billing.change_email`は課金のメールが変更されたすべてのイベントを検索します。 +* `action:team.create` finds all events where a team was created. +* `-action:billing.change_email` excludes all events where the billing email was changed. -### 場所に基づく検索 +### Search based on the location -`country`修飾子は、発生元の国によってアクションをフィルタリングします。 -- 国の 2 文字のショートコードまたはフル ネームを使用できます。 -- 名前に空白を含む国は、引用符で囲まなければなりません。 例: - * `country:de` は、ドイツで発生したイベントをすべて検索します。 - * `country:Mexico` はメキシコで発生したすべてのイベントを検索します。 - * `country:"United States"` はアメリカ合衆国で発生したすべてのイベントを検索します。 +The `country` qualifier filters actions by the originating country. +- You can use a country's two-letter short code or its full name. +- Countries with spaces in their name must be wrapped in quotation marks. For example: + * `country:de` finds all events that occurred in Germany. + * `country:Mexico` finds all events that occurred in Mexico. + * `country:"United States"` all finds events that occurred in the United States. -### アクションの時刻に基づく検索 +### Search based on the time of action -`created`修飾子は、発生した時刻でアクションをフィルタリングします。 -- 日付には `YYYY-MM-DD` という形式を使います。これは、年の後に月、その後に日が続きます。 -- 日付では[大なり、小なりおよび範囲指定](/enterprise/{{ currentVersion }}/user/articles/search-syntax)を使用できます。 例: - * `created:2014-07-08` は、2014 年 7 月 8 日に発生したイベントをすべて検索します。 - * `created:>=2014-07-01` は、2014 年 7 月 1 日かそれ以降に生じたすべてのイベントを検索します。 - * `created:<=2014-07-01`は、2014 年 7 月 1 日かそれ以前に生じたすべてのイベントを検索します。 - * `created:2014-07-01..2014-07-31`は、2014 年 7 月に起きたすべてのイベントを検索します。 +The `created` qualifier filters actions by the time they occurred. +- Define dates using the format of `YYYY-MM-DD`--that's year, followed by month, followed by day. +- Dates support [greater than, less than, and range qualifiers](/enterprise/{{ currentVersion }}/user/articles/search-syntax). For example: + * `created:2014-07-08` finds all events that occurred on July 8th, 2014. + * `created:>=2014-07-01` finds all events that occurred on or after July 8th, 2014. + * `created:<=2014-07-01` finds all events that occurred on or before July 8th, 2014. + * `created:2014-07-01..2014-07-31` finds all events that occurred in the month of July 2014. diff --git a/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/customizing-user-messages-for-your-enterprise.md b/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/customizing-user-messages-for-your-enterprise.md index a6c6136f9b22..f6396f94cca2 100644 --- a/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/customizing-user-messages-for-your-enterprise.md +++ b/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/customizing-user-messages-for-your-enterprise.md @@ -1,12 +1,12 @@ --- -title: Enterprise のユーザメッセージをカスタマイズする +title: Customizing user messages for your enterprise shortTitle: Customizing user messages redirect_from: - - /enterprise/admin/user-management/creating-a-custom-sign-in-message/ + - /enterprise/admin/user-management/creating-a-custom-sign-in-message - /enterprise/admin/user-management/customizing-user-messages-on-your-instance - /admin/user-management/customizing-user-messages-on-your-instance - /admin/user-management/customizing-user-messages-for-your-enterprise -intro: '{% data variables.product.product_location %} でユーザに表示されるカスタムメッセージを作成できます。' +intro: 'You can create custom messages that users will see on {% data variables.product.product_location %}.' versions: ghes: '*' ghae: '*' @@ -15,64 +15,69 @@ topics: - Enterprise - Maintenance --- +## About user messages -## ユーザメッセージについて - -ユーザメッセージにはいくつかの種類があります。 -- {% ifversion ghes %}サインインまたは{% endif %}サインアウトページ{% ifversion ghes or ghae %}に表示されるメッセージ +There are several types of user messages. +- Messages that appear on the {% ifversion ghes %}sign in or {% endif %}sign out page{% ifversion ghes or ghae %} - Mandatory messages, which appear once in a pop-up window that must be dismissed{% endif %}{% ifversion ghes or ghae %} -- すべてのページの上部に表示されるアナウンスバナー{% endif %} +- Announcement banners, which appear at the top of every page{% endif %} {% ifversion ghes %} {% note %} -**メモ:** 認証に SAML を使っている場合は、サインインページはアイデンティティプロバイダによって提示されるため、{% data variables.product.prodname_ghe_server %} でカスタマイズすることはできません。 +**Note:** If you are using SAML for authentication, the sign in page is presented by your identity provider and is not customizable via {% data variables.product.prodname_ghe_server %}. {% endnote %} -メッセージの書式設定には Markdown を使用できます。 詳しい情報については、「[{% data variables.product.prodname_dotcom %}での執筆とフォーマットについて](/articles/about-writing-and-formatting-on-github/)」を参照してください。 +You can use Markdown to format your message. For more information, see "[About writing and formatting on {% data variables.product.prodname_dotcom %}](/articles/about-writing-and-formatting-on-github/)." -## カスタムサインインメッセージの作成 +## Creating a custom sign in message {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.messages-tab %} -5. {% ifversion ghes %}[Sign in page] の右側{% else %}下{% endif %}にある [**Add message**] または [**Edit message**] をクリックします。 ![{% ifversion ghes %}[Add]{% else %}[Edit]{% endif %} メッセージボタン](/assets/images/enterprise/site-admin-settings/edit-message.png) -6. [**Sign in message**] の下に、ユーザに見せたいメッセージを入力します。 ![Sign in message](/assets/images/enterprise/site-admin-settings/sign-in-message.png){% ifversion ghes %} +5. {% ifversion ghes %}To the right of{% else %}Under{% endif %} "Sign in page", click **Add message** or **Edit message**. +![{% ifversion ghes %}Add{% else %}Edit{% endif %} message button](/assets/images/enterprise/site-admin-settings/edit-message.png) +6. Under **Sign in message**, type the message you'd like users to see. +![Sign in message](/assets/images/enterprise/site-admin-settings/sign-in-message.png){% ifversion ghes %} {% data reusables.enterprise_site_admin_settings.message-preview-save %}{% else %} {% data reusables.enterprise_site_admin_settings.click-preview %} - ![プレビューボタン](/assets/images/enterprise/site-admin-settings/sign-in-message-preview-button.png) -8. 表示されたメッセージを確認します。 ![サインインメッセージの表示](/assets/images/enterprise/site-admin-settings/sign-in-message-rendered.png) + ![Preview button](/assets/images/enterprise/site-admin-settings/sign-in-message-preview-button.png) +8. Review the rendered message. +![Sign in message rendered](/assets/images/enterprise/site-admin-settings/sign-in-message-rendered.png) {% data reusables.enterprise_site_admin_settings.save-changes %}{% endif %} {% endif %} -## カスタムサインアウトメッセージを作成する +## Creating a custom sign out message {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.messages-tab %} -5. {% ifversion ghes or ghae %}[Sign in page] の右側{% else %}下{% endif %}にある [**Add message**] または [**Edit message**] をクリックします。 ![[Add message] ボタン](/assets/images/enterprise/site-admin-settings/sign-out-add-message-button.png) -6. [**Sign out message**] の下に、ユーザに見せたいメッセージを入力します。 ![Sign two_factor_auth_header message](/assets/images/enterprise/site-admin-settings/sign-out-message.png){% ifversion ghes or ghae %} +5. {% ifversion ghes or ghae %}To the right of{% else %}Under{% endif %} "Sign out page", click **Add message** or **Edit message**. +![Add message button](/assets/images/enterprise/site-admin-settings/sign-out-add-message-button.png) +6. Under **Sign out message**, type the message you'd like users to see. +![Sign two_factor_auth_header message](/assets/images/enterprise/site-admin-settings/sign-out-message.png){% ifversion ghes or ghae %} {% data reusables.enterprise_site_admin_settings.message-preview-save %}{% else %} {% data reusables.enterprise_site_admin_settings.click-preview %} - ![プレビューボタン](/assets/images/enterprise/site-admin-settings/sign-out-message-preview-button.png) -8. 表示されたメッセージを確認します。 ![サインアウトメッセージの表示](/assets/images/enterprise/site-admin-settings/sign-out-message-rendered.png) + ![Preview button](/assets/images/enterprise/site-admin-settings/sign-out-message-preview-button.png) +8. Review the rendered message. +![Sign out message rendered](/assets/images/enterprise/site-admin-settings/sign-out-message-rendered.png) {% data reusables.enterprise_site_admin_settings.save-changes %}{% endif %} {% ifversion ghes or ghae %} -## 必須メッセージを作成する +## Creating a mandatory message -メッセージを保存した後に初めてサインインしたときに、すべてのユーザに表示される必須メッセージを {% data variables.product.product_name %} で作成できます。 メッセージはポップアップウィンドウ内に表示され、ユーザは {% data variables.product.product_location %} を使用する前に閉じる必要があります。 +You can create a mandatory message that {% data variables.product.product_name %} will show to all users the first time they sign in after you save the message. The message appears in a pop-up window that the user must dismiss before the user can use {% data variables.product.product_location %}. -必須メッセージにはさまざまな用途があります。 +Mandatory messages have a variety of uses. -- 新入社員にオンボーディング情報を提供する -- {% data variables.product.product_location %} のヘルプの取得方法をユーザに伝える -- すべてのユーザが {% data variables.product.product_location %} を使用時の利用規約を確実に読むようにする +- Providing onboarding information for new employees +- Telling users how to get help with {% data variables.product.product_location %} +- Ensuring that all users read your terms of service for using {% data variables.product.product_location %} -メッセージに Markdown チェックボックスを含める場合、ユーザがメッセージを閉じる前に、すべてのチェックボックスを選択する必要があります。 たとえば、必須メッセージに利用規約を含める場合、各ユーザにチェックボックスを選択して、ユーザが利用規約を読んだことを確認するように要求できます。 +If you include Markdown checkboxes in the message, all checkboxes must be selected before the user can dismiss the message. For example, if you include your terms of service in the mandatory message, you can require that each user selects a checkbox to confirm the user has read the terms. -ユーザに必須メッセージが表示されるたびに、監査ログイベントが作成されます。 イベントには、ユーザが表示したメッセージのバージョンが含まれます。 詳しい情報については、「[監査されたアクション](/admin/user-management/audited-actions)」を参照してください。 +Each time a user sees a mandatory message, an audit log event is created. The event includes the version of the message that the user saw. For more information see "[Audited actions](/admin/user-management/audited-actions)." {% note %} @@ -83,30 +88,35 @@ topics: {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.messages-tab %} -1. [Mandatory message] の右側にある [**Add message**] をクリックします。 ![Add mandatory message button](/assets/images/enterprise/site-admin-settings/add-mandatory-message-button.png) -1. [Mandatory message] の下のテキストボックスに、メッセージを入力します。 ![Mandatory message text box](/assets/images/enterprise/site-admin-settings/mandatory-message-text-box.png) +1. To the right of "Mandatory message", click **Add message**. + ![Add mandatory message button](/assets/images/enterprise/site-admin-settings/add-mandatory-message-button.png) +1. Under "Mandatory message", in the text box, type your message. + ![Mandatory message text box](/assets/images/enterprise/site-admin-settings/mandatory-message-text-box.png) {% data reusables.enterprise_site_admin_settings.message-preview-save %} {% endif %} {% ifversion ghes or ghae %} -## グローバルアナウンスバナーを作成する +## Creating a global announcement banner -各ページの上部にグローバルアナウンスバナーを設定し、すべてのユーザに対して表示できます。 +You can set a global announcement banner to be displayed to all users at the top of every page. {% ifversion ghae or ghes %} -You can also set an announcement banner{% ifversion ghes %} in the administrative shell using a command line utility or{% endif %} using the API. 詳しい情報については、{% ifversion ghes %}「[コマンドラインユーティリティ](/enterprise/admin/configuration/command-line-utilities#ghe-announce)」および{% endif %}「[{% data variables.product.prodname_enterprise %} 管理](/rest/reference/enterprise-admin#announcements)」を参照してください。 +You can also set an announcement banner{% ifversion ghes %} in the administrative shell using a command line utility or{% endif %} using the API. For more information, see {% ifversion ghes %}"[Command-line utilities](/enterprise/admin/configuration/command-line-utilities#ghe-announce)" and {% endif %}"[{% data variables.product.prodname_enterprise %} administration](/rest/reference/enterprise-admin#announcements)." {% else %} -コマンドラインユーティリティを使用して、管理シェルでアナウンスバナーを設定することもできます。 詳しい情報については、「[コマンドラインユーティリティ](/enterprise/admin/configuration/command-line-utilities#ghe-announce)」を参照してください。 +You can also set an announcement banner in the administrative shell using a command line utility. For more information, see "[Command-line utilities](/enterprise/admin/configuration/command-line-utilities#ghe-announce)." {% endif %} {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.messages-tab %} -1. {% ifversion ghes or ghae %}[Announcement] の右側{% else %}下{% endif %}にある [**Add announcement**] をクリックします。 ![[Add message] ボタン](/assets/images/enterprise/site-admin-settings/add-announcement-button.png) -1. [Announcement] のテキストフィールドに、バナーに表示するお知らせを入力します。 ![アナウンスを入力するテキストフィールド](/assets/images/enterprise/site-admin-settings/announcement-text-field.png) -1. 必要に応じて、[Expires on] でカレンダーのドロップダウンメニューを選択し、有効期限をクリックします。 ![有効期限を選択するためのカレンダードロップダウンメニュー](/assets/images/enterprise/site-admin-settings/expiration-drop-down.png) +1. {% ifversion ghes or ghae %}To the right of{% else %}Under{% endif %} "Announcement", click **Add announcement**. + ![Add announcement button](/assets/images/enterprise/site-admin-settings/add-announcement-button.png) +1. Under "Announcement", in the text field, type the announcement you want displayed in a banner. + ![Text field to enter announcement](/assets/images/enterprise/site-admin-settings/announcement-text-field.png) +1. Optionally, under "Expires on", select the calendar drop-down menu and click an expiration date. + ![Calendar drop-down menu to choose expiration date](/assets/images/enterprise/site-admin-settings/expiration-drop-down.png) {% data reusables.enterprise_site_admin_settings.message-preview-save %} {% endif %} diff --git a/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/index.md b/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/index.md index 5e489654da3b..4b8443a83452 100644 --- a/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/index.md +++ b/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/index.md @@ -1,9 +1,9 @@ --- -title: Enterprise のユーザを管理する -intro: ユーザアクティビティを監査し、ユーザ設定を管理できます。 +title: Managing users in your enterprise +intro: You can audit user activity and manage user settings. redirect_from: - /github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise - - /enterprise/admin/guides/user-management/enabling-avatars-and-identicons/ + - /enterprise/admin/guides/user-management/enabling-avatars-and-identicons - /enterprise/admin/user-management/basic-account-settings - /enterprise/admin/user-management/user-security - /enterprise/admin/user-management/managing-users-in-your-enterprise @@ -35,4 +35,3 @@ children: - /rebuilding-contributions-data shortTitle: Manage users --- - diff --git a/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/inviting-people-to-manage-your-enterprise.md b/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/inviting-people-to-manage-your-enterprise.md index f1ca02ce022e..bdb7d0b4f927 100644 --- a/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/inviting-people-to-manage-your-enterprise.md +++ b/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/inviting-people-to-manage-your-enterprise.md @@ -1,12 +1,12 @@ --- -title: Enterprise を管理するようユーザを招待する +title: Inviting people to manage your enterprise intro: 'You can {% ifversion ghec %}invite people to become enterprise owners or billing managers for{% elsif ghes %}add enterprise owners to{% endif %} your enterprise account. You can also remove enterprise owners {% ifversion ghec %}or billing managers {% endif %}who no longer need access to the enterprise account.' product: '{% data reusables.gated-features.enterprise-accounts %}' permissions: 'Enterprise owners can {% ifversion ghec %}invite other people to become{% elsif ghes %}add{% endif %} additional enterprise administrators.' redirect_from: - /github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/inviting-people-to-manage-your-enterprise - /github/setting-up-and-managing-your-enterprise-account/inviting-people-to-manage-your-enterprise-account - - /articles/inviting-people-to-collaborate-in-your-business-account/ + - /articles/inviting-people-to-collaborate-in-your-business-account - /articles/inviting-people-to-manage-your-enterprise-account - /github/setting-up-and-managing-your-enterprise/inviting-people-to-manage-your-enterprise versions: @@ -38,7 +38,7 @@ If your enterprise uses {% data variables.product.prodname_emus %}, enterprise o {% tip %} -**ヒント:** Enterprise アカウントが所有する Organization 内のユーザを管理する方法に関する詳しい情報については、「[Organization でメンバーシップを管理する](/articles/managing-membership-in-your-organization)」および「[Organization への人々のアクセスをロールで管理する](/articles/managing-peoples-access-to-your-organization-with-roles)」を参照してください。 +**Tip:** For more information on managing users within an organization owned by your enterprise account, see "[Managing membership in your organization](/articles/managing-membership-in-your-organization)" and "[Managing people's access to your organization with roles](/articles/managing-peoples-access-to-your-organization-with-roles)." {% endtip %} @@ -48,28 +48,33 @@ If your enterprise uses {% data variables.product.prodname_emus %}, enterprise o {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.people-tab %} -1. 左サイドバーで [**Administrators**] をクリックします。 ![左サイドバーの [Administrators] タブ](/assets/images/help/business-accounts/administrators-tab.png) +1. In the left sidebar, click **Administrators**. + ![Administrators tab in the left sidebar](/assets/images/help/business-accounts/administrators-tab.png) 1. Above the list of administrators, click {% ifversion ghec %}**Invite admin**{% elsif ghes %}**Add owner**{% endif %}. {% ifversion ghec %} !["Invite admin" button above the list of enterprise owners](/assets/images/help/business-accounts/invite-admin-button.png) {% elsif ghes %} !["Add owner" button above the list of enterprise owners](/assets/images/help/business-accounts/add-owner-button.png) {% endif %} -1. Enterprise 管理者として招待する人のユーザ名、フルネーム、またはメール アドレスを入力して、表示された結果から適切な人を選びます。 ![Modal box with field to type a person's username, full name, or email address, and Invite button](/assets/images/help/business-accounts/invite-admins-modal-button.png){% ifversion ghec %} -1. [**Owner**] または [**Billing Manager**] を選択します。 ![ロールの選択肢が表示されたモーダルボックス](/assets/images/help/business-accounts/invite-admins-roles.png) -1. [**Send Invitation**] をクリックします。 ![Send invitation button](/assets/images/help/business-accounts/invite-admins-send-invitation.png){% endif %}{% ifversion ghes %} -1. [**Add**] をクリックします。 !["Add" button](/assets/images/help/business-accounts/add-administrator-add-button.png){% endif %} +1. Type the username, full name, or email address of the person you want to invite to become an enterprise administrator, then select the appropriate person from the results. + ![Modal box with field to type a person's username, full name, or email address, and Invite button](/assets/images/help/business-accounts/invite-admins-modal-button.png){% ifversion ghec %} +1. Select **Owner** or **Billing Manager**. + ![Modal box with role choices](/assets/images/help/business-accounts/invite-admins-roles.png) +1. Click **Send Invitation**. + ![Send invitation button](/assets/images/help/business-accounts/invite-admins-send-invitation.png){% endif %}{% ifversion ghes %} +1. Click **Add**. + !["Add" button](/assets/images/help/business-accounts/add-administrator-add-button.png){% endif %} -## Enterprise アカウントから Enterprise 管理者を削除する +## Removing an enterprise administrator from your enterprise account -Enterprise アカウントから他の Enterprise 管理者を削除できるのは、Enterprise オーナーだけです。 +Only enterprise owners can remove other enterprise administrators from the enterprise account. {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.people-tab %} 1. Next to the username of the person you'd like to remove, click {% octicon "gear" aria-label="The Settings gear" %}, then click **Remove owner**{% ifversion ghec %} or **Remove billing manager**{% endif %}. {% ifversion ghec %} - ![Enterprise 管理者を削除するためのメニュー オプション付きの設定「歯車」アイコン](/assets/images/help/business-accounts/remove-admin.png) + ![Settings gear with menu option to remove an enterprise administrator](/assets/images/help/business-accounts/remove-admin.png) {% elsif ghes %} - ![Enterprise 管理者を削除するためのメニュー オプション付きの設定「歯車」アイコン](/assets/images/help/business-accounts/ghes-remove-owner.png) + ![Settings gear with menu option to remove an enterprise administrator](/assets/images/help/business-accounts/ghes-remove-owner.png) {% endif %} 1. Read the confirmation, then click **Remove owner**{% ifversion ghec %} or **Remove billing manager**{% endif %}. diff --git a/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/managing-dormant-users.md b/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/managing-dormant-users.md index d0bf2fe0a032..ce92ba1dc446 100644 --- a/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/managing-dormant-users.md +++ b/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/managing-dormant-users.md @@ -1,9 +1,9 @@ --- -title: 休眠ユーザの管理 +title: Managing dormant users redirect_from: - - /enterprise/admin/articles/dormant-users/ - - /enterprise/admin/articles/viewing-dormant-users/ - - /enterprise/admin/articles/determining-whether-a-user-account-is-dormant/ + - /enterprise/admin/articles/dormant-users + - /enterprise/admin/articles/viewing-dormant-users + - /enterprise/admin/articles/determining-whether-a-user-account-is-dormant - /enterprise/admin/user-management/managing-dormant-users - /admin/user-management/managing-dormant-users intro: '{% data reusables.enterprise-accounts.dormant-user-activity-threshold %}' @@ -17,26 +17,29 @@ topics: - Enterprise - Licensing --- - {% data reusables.enterprise-accounts.dormant-user-activity %} {% ifversion ghes or ghae%} -## 休眠ユーザの表示 +## Viewing dormant users {% data reusables.enterprise-accounts.viewing-dormant-users %} {% data reusables.enterprise_site_admin_settings.access-settings %} -3. 左のサイドバーで**Dormant users（休眠ユーザ）**をクリックしてください。 ![Dormant users tab](/assets/images/enterprise/site-admin-settings/dormant-users-tab.png){% ifversion ghes %} -4. このリスト中のすべての休眠ユーザをサスペンドするには、ページの上部で**Suspend all（全員をサスペンド）**をクリックしてください。 ![Suspend all button](/assets/images/enterprise/site-admin-settings/suspend-all.png){% endif %} +3. In the left sidebar, click **Dormant users**. +![Dormant users tab](/assets/images/enterprise/site-admin-settings/dormant-users-tab.png){% ifversion ghes %} +4. To suspend all the dormant users in this list, at the top of the page, click **Suspend all**. +![Suspend all button](/assets/images/enterprise/site-admin-settings/suspend-all.png){% endif %} -## ユーザアカウントが休眠状態かの判断 +## Determining whether a user account is dormant {% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.search-user %} {% data reusables.enterprise_site_admin_settings.click-user %} -5. **User info（ユーザ情報）**セクションで"Dormant（休眠）"という語の付いた赤い点は、そのユーザアカウントが休眠状態であることを示し、"Active（アクティブ）"という語の付いた緑の点はそのユーザアカウントがアクティブであることを示します。 ![休眠ユーザアカウント](/assets/images/enterprise/stafftools/dormant-user.png) ![アクティブなユーザアカウント](/assets/images/enterprise/stafftools/active-user.png) +5. In the **User info** section, a red dot with the word "Dormant" indicates the user account is dormant, and a green dot with the word "Active" indicates the user account is active. +![Dormant user account](/assets/images/enterprise/stafftools/dormant-user.png) +![Active user account](/assets/images/enterprise/stafftools/active-user.png) -## 休眠の閾値の設定 +## Configuring the dormancy threshold {% data reusables.enterprise_site_admin_settings.dormancy-threshold %} @@ -44,7 +47,8 @@ topics: {% data reusables.enterprise-accounts.policies-tab %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.options-tab %} -4. [Dormancy threshold] の下で、ドロップダウンメニューを使って、希望する休眠閾値をクリックします。 ![休眠の閾値のドロップダウンメニュー](/assets/images/enterprise/site-admin-settings/dormancy-threshold-menu.png) +4. Under "Dormancy threshold", use the drop-down menu, and click the desired dormancy threshold. +![The Dormancy threshold drop-down menu](/assets/images/enterprise/site-admin-settings/dormancy-threshold-menu.png) {% endif %} @@ -62,6 +66,7 @@ topics: {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.enterprise-accounts-compliance-tab %} -1. To download your Dormant Users (beta) report as a CSV file, under "Other", click {% octicon "download" aria-label="The Download icon" %} **Download**. ![Download button under "Other" on the Compliance page](/assets/images/help/business-accounts/dormant-users-download-button.png) +1. To download your Dormant Users (beta) report as a CSV file, under "Other", click {% octicon "download" aria-label="The Download icon" %} **Download**. + ![Download button under "Other" on the Compliance page](/assets/images/help/business-accounts/dormant-users-download-button.png) {% endif %} diff --git a/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/promoting-or-demoting-a-site-administrator.md b/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/promoting-or-demoting-a-site-administrator.md index 780a4f41911c..0227145d6880 100644 --- a/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/promoting-or-demoting-a-site-administrator.md +++ b/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/promoting-or-demoting-a-site-administrator.md @@ -1,8 +1,8 @@ --- title: Promoting or demoting a site administrator redirect_from: - - /enterprise/admin/articles/promoting-a-site-administrator/ - - /enterprise/admin/articles/demoting-a-site-administrator/ + - /enterprise/admin/articles/promoting-a-site-administrator + - /enterprise/admin/articles/demoting-a-site-administrator - /enterprise/admin/user-management/promoting-or-demoting-a-site-administrator - /admin/user-management/promoting-or-demoting-a-site-administrator intro: 'Site administrators can promote any normal user account to a site administrator, as well as demote other site administrators to regular users.' diff --git a/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/rebuilding-contributions-data.md b/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/rebuilding-contributions-data.md index 760f69d02205..fc57c1bf125b 100644 --- a/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/rebuilding-contributions-data.md +++ b/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/rebuilding-contributions-data.md @@ -1,8 +1,8 @@ --- -title: コントリビューションデータの再構築 -intro: 既存のコミットをユーザアカウントにリンクするために、コントリビューションデータの再構築が必要になることがあります。 +title: Rebuilding contributions data +intro: You may need to rebuild contributions data to link existing commits to a user account. redirect_from: - - /enterprise/admin/articles/rebuilding-contributions-data/ + - /enterprise/admin/articles/rebuilding-contributions-data - /enterprise/admin/user-management/rebuilding-contributions-data - /admin/user-management/rebuilding-contributions-data versions: @@ -14,13 +14,14 @@ topics: - User account shortTitle: Rebuild contributions --- +Whenever a commit is pushed to {% data variables.product.prodname_enterprise %}, it is linked to a user account if they are both associated with the same email address. However, existing commits are *not* retroactively linked when a user registers a new email address or creates a new account. -コミットは、{% data variables.product.prodname_enterprise %}にプッシュされるたびに、プッシュのメールアドレスとユーザのメールアドレスが同じ場合は、ユーザアカウントに関連付けられます。 しかし、ユーザが新規メールアドレスの登録や新規アカウントの作成をした場合、既存のコミットは、遡及的には関連付けられ*ません*。 - -1. ユーザのプロフィールページにアクセスします。 +1. Visit the user's profile page. {% data reusables.enterprise_site_admin_settings.access-settings %} -3. ページ左にある、**Admin** をクリックする。 ![[Admin] タブ](/assets/images/enterprise/site-admin-settings/admin-tab.png) -4. **Contributions data** で、**Rebuild** をクリックする。 ![[Rebuild] ボタン](/assets/images/enterprise/site-admin-settings/rebuild-button.png) +3. On the left side of the page, click **Admin**. + ![Admin tab](/assets/images/enterprise/site-admin-settings/admin-tab.png) +4. Under **Contributions data**, click **Rebuild**. +![Rebuild button](/assets/images/enterprise/site-admin-settings/rebuild-button.png) -{% data variables.product.prodname_enterprise %} は、コミットをユーザアカウントに再度リンクするためのバックグラウンドジョブを開始します。 - ![待ち行列に入っている再構築ジョブ](/assets/images/enterprise/site-admin-settings/rebuild-jobs.png) +{% data variables.product.prodname_enterprise %} will now start background jobs to re-link commits with that user's account. + ![Queued rebuild jobs](/assets/images/enterprise/site-admin-settings/rebuild-jobs.png) diff --git a/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise.md b/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise.md index 653d27e13a31..e1586d12d05b 100644 --- a/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise.md +++ b/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise.md @@ -1,11 +1,11 @@ --- -title: Enterprise におけるロール -intro: Enterprise 内の全員が Enterprise のメンバーです。 Enterprise の設定とデータへのアクセスを制御するために、Enterprise のメンバーにさまざまなロールを割り当てることができます。 +title: Roles in an enterprise +intro: 'Everyone in an enterprise is a member of the enterprise. To control access to your enterprise''s settings and data, you can assign different roles to members of your enterprise.' product: '{% data reusables.gated-features.enterprise-accounts %}' redirect_from: - /github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/roles-in-an-enterprise - /github/setting-up-and-managing-your-enterprise-account/roles-for-an-enterprise-account - - /articles/permission-levels-for-a-business-account/ + - /articles/permission-levels-for-a-business-account - /articles/roles-for-an-enterprise-account - /github/setting-up-and-managing-your-enterprise/roles-in-an-enterprise versions: @@ -16,9 +16,9 @@ topics: - Enterprise --- -## Enterprise のロールについて +## About roles in an enterprise -Enterprise 内の全員が Enterprise のメンバーです。 Enterprise のメンバーに管理者のロールを割り当てることもできます。 各管理者ロールはビジネス機能にマップされ、Enterprise 内の特定のタスクを行う権限を与えます。 +Everyone in an enterprise is a member of the enterprise. You can also assign administrative roles to members of your enterprise. Each administrator role maps to business functions and provides permissions to do specific tasks within the enterprise. {% data reusables.enterprise-accounts.enterprise-administrators %} @@ -31,46 +31,46 @@ For more information about adding people to your enterprise, see "[Authenticatio {% endif %} -## Enterprise オーナー +## Enterprise owner -Enterprise オーナーは、Enterprise の完全な管理権限を持ち、以下を含むすべての操作を行うことができます。 -- 管理者を管理する -- {% ifversion ghec %}追加と削除 {% elsif ghae or ghes %} Enterprise {% endif %}{% ifversion ghec %}内および {% elsif ghae or ghes %}Enterprise{% endif %} 内から Organization を管理する -- Enterprise 設定を管理する -- Organization にポリシーを強制する -{% ifversion ghec %}- 支払い設定を管理する{% endif %} +Enterprise owners have complete control over the enterprise and can take every action, including: +- Managing administrators +- {% ifversion ghec %}Adding and removing {% elsif ghae or ghes %}Managing{% endif %} organizations {% ifversion ghec %}to and from {% elsif ghae or ghes %} in{% endif %} the enterprise +- Managing enterprise settings +- Enforcing policy across organizations +{% ifversion ghec %}- Managing billing settings{% endif %} -Enterprise オーナーは、Organization のオーナーになるか、Organization が所有するリポジトリに直接アクセスする権限を与えられない限り、Organization の設定またはコンテンツにはアクセスできません。 同様に、Enterprise の Organization のオーナーは、Enterprise のオーナーにならない限り、Enterprise にはアクセスできません。 +Enterprise owners cannot access organization settings or content unless they are made an organization owner or given direct access to an organization-owned repository. Similarly, owners of organizations in your enterprise do not have access to the enterprise itself unless you make them enterprise owners. -Enterprise のオーナーは、Enterprise 内の少なくとも 1 つの Organization のオーナーまたはメンバーである場合にのみ、ライセンスを消費できます。 {% ifversion ghec %}Enterprise のオーナーは {% data variables.product.prodname_dotcom %} に個人アカウントを持っている必要があります。{% endif %} ベストプラクティスとして、ビジネスへのリスクを軽減するために、Enterprise のオーナーを数人にすることをお勧めします。 +An enterprise owner will only consume a license if they are an owner or member of at least one organization within the enterprise. {% ifversion ghec %}Enterprise owners must have a personal account on {% data variables.product.prodname_dotcom %}.{% endif %} As a best practice, we recommend making only a few people in your company enterprise owners, to reduce the risk to your business. -## Enterprise メンバー +## Enterprise members -Enterprise が所有する Organization のメンバーも、自動的に Enterprise のメンバーになります。 メンバーは Organization 内でコラボレートできます。Organization のオーナーになることも可能です。メンバーは支払い設定を含む Enterprise 設定{% ifversion ghec %}にアクセスまたは設定することはできません。{% endif %} +Members of organizations owned by your enterprise are also automatically members of the enterprise. Members can collaborate in organizations and may be organization owners, but members cannot access or configure enterprise settings{% ifversion ghec %}, including billing settings{% endif %}. -Enterprise 内のユーザは、Enterprise が所有するさまざまな Organization およびそれらの Organization 内のリポジトリへのあらゆるレベルのアクセス権を持つことができます。 各個人がアクセスできるリソースを確認することができます。 詳しい情報については、「[Enterprise の人を表示する](/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise)」を参照してください。 +People in your enterprise may have different levels of access to the various organizations owned by your enterprise and to repositories within those organizations. You can view the resources that each person has access to. For more information, see "[Viewing people in your enterprise](/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise)." For more information about organization-level permissions, see "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)." -Organization が所有するリポジトリへの外部のコラボレータアクセス権を持つユーザも、Enterprise の [People] タブに一覧表示されますが、Enterprise メンバーではなく、Enterprise へのアクセス権はありません。 For more information about outside collaborators, see "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization#outside-collaborators)." +People with outside collaborator access to repositories owned by your organization are also listed in your enterprise's People tab, but are not enterprise members and do not have any access to the enterprise. For more information about outside collaborators, see "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization#outside-collaborators)." {% ifversion ghec %} -## 支払いマネージャー +## Billing manager -支払いマネージャーは、Enterprise の支払い設定にのみアクセスできます。 Enterprise の支払いマネージャーは次の操作ができます。 -- ユーザライセンス、{% data variables.large_files.product_name_short %} パック、およびその他の支払い設定の閲覧および管理 -- 支払いマネージャーのリストを閲覧 -- 他の支払いマネージャーの追加または削除 +Billing managers only have access to your enterprise's billing settings. Billing managers for your enterprise can: +- View and manage user licenses, {% data variables.large_files.product_name_short %} packs and other billing settings +- View a list of billing managers +- Add or remove other billing managers -支払いマネージャーは、Enterprise 内の少なくとも 1 つの Organization のオーナーまたはメンバーである場合にのみ、ライセンスを消費できます。 支払いマネージャーは、Enterprise の Organization またはリポジトリにアクセスすることはできません。また、Enterprise のオーナーを追加または削除することもできません。 支払いマネージャーは、{% data variables.product.prodname_dotcom %} 上に個人アカウントを持っていなければなりません。 +Billing managers will only consume a license if they are an owner or member of at least one organization within the enterprise. Billing managers do not have access to organizations or repositories in your enterprise, and cannot add or remove enterprise owners. Billing managers must have a personal account on {% data variables.product.prodname_dotcom %}. ## About support entitlements {% data reusables.enterprise-accounts.support-entitlements %} -## 参考リンク +## Further reading -- 「[Enterprise アカウントについて](/admin/overview/about-enterprise-accounts)」 +- "[About enterprise accounts](/admin/overview/about-enterprise-accounts)" {% endif %} diff --git a/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/suspending-and-unsuspending-users.md b/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/suspending-and-unsuspending-users.md index 08148b0c9f52..f64cdf6334d7 100644 --- a/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/suspending-and-unsuspending-users.md +++ b/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/suspending-and-unsuspending-users.md @@ -1,11 +1,11 @@ --- title: Suspending and unsuspending users redirect_from: - - /enterprise/admin/articles/suspending-a-user/ - - /enterprise/admin/articles/unsuspending-a-user/ - - /enterprise/admin/articles/viewing-suspended-users/ - - /enterprise/admin/articles/suspended-users/ - - /enterprise/admin/articles/suspending-and-unsuspending-users/ + - /enterprise/admin/articles/suspending-a-user + - /enterprise/admin/articles/unsuspending-a-user + - /enterprise/admin/articles/viewing-suspended-users + - /enterprise/admin/articles/suspended-users + - /enterprise/admin/articles/suspending-and-unsuspending-users - /enterprise/admin/user-management/suspending-and-unsuspending-users - /admin/user-management/suspending-and-unsuspending-users intro: 'If a user leaves or moves to a different part of the company, you should remove or modify their ability to access {% data variables.product.product_location %}.' diff --git a/translations/ja-JP/content/admin/user-management/monitoring-activity-in-your-enterprise/activity-dashboard.md b/translations/ja-JP/content/admin/user-management/monitoring-activity-in-your-enterprise/activity-dashboard.md index 885f9422cb9d..edc50c6daa64 100644 --- a/translations/ja-JP/content/admin/user-management/monitoring-activity-in-your-enterprise/activity-dashboard.md +++ b/translations/ja-JP/content/admin/user-management/monitoring-activity-in-your-enterprise/activity-dashboard.md @@ -1,8 +1,8 @@ --- -title: アクティビティダッシュボード -intro: アクティビティダッシュボードで、Enterprise 内のすべてのアクティビティの概要を確認できます。 +title: Activity dashboard +intro: The Activity dashboard gives you an overview of all the activity in your enterprise. redirect_from: - - /enterprise/admin/articles/activity-dashboard/ + - /enterprise/admin/articles/activity-dashboard - /enterprise/admin/installation/activity-dashboard - /enterprise/admin/user-management/activity-dashboard - /admin/user-management/activity-dashboard @@ -12,21 +12,22 @@ versions: topics: - Enterprise --- +The Activity dashboard provides weekly, monthly, and yearly graphs of the number of: +- New pull requests +- Merged pull requests +- New issues +- Closed issues +- New issue comments +- New repositories +- New user accounts +- New organizations +- New teams -アクティビティダッシュボードには、次の数値の週次、月次、年次のグラフが表示されます。 -- 新規プルリクエスト -- マージされたプルリクエスト -- 新規 Issue -- 解決された Issue -- 新規 Issue コメント -- 新規リポジトリ -- 新規ユーザアカウント -- 新規 Organization -- 新規 Team +![Activity dashboard](/assets/images/enterprise/activity/activity-dashboard-yearly.png) -![アクティビティダッシュボード](/assets/images/enterprise/activity/activity-dashboard-yearly.png) +## Accessing the Activity dashboard -## アクティビティダッシュボードへのアクセス - -1. ページの上部で [**Explore**] をクリックします。 ![[Explore] タブ](/assets/images/enterprise/settings/ent-new-explore.png) -2. 右上にある **Activity** をクリックする。 ![Activity ボタン](/assets/images/enterprise/activity/activity-button.png) +1. At the top of any page, click **Explore**. +![Explore tab](/assets/images/enterprise/settings/ent-new-explore.png) +2. In the upper-right corner, click **Activity**. +![Activity button](/assets/images/enterprise/activity/activity-button.png) diff --git a/translations/ja-JP/content/admin/user-management/monitoring-activity-in-your-enterprise/audit-logging.md b/translations/ja-JP/content/admin/user-management/monitoring-activity-in-your-enterprise/audit-logging.md index fc17c13ff77b..0b39b98872e0 100644 --- a/translations/ja-JP/content/admin/user-management/monitoring-activity-in-your-enterprise/audit-logging.md +++ b/translations/ja-JP/content/admin/user-management/monitoring-activity-in-your-enterprise/audit-logging.md @@ -1,8 +1,8 @@ --- -title: 監査ログ -intro: '{% data variables.product.product_name %} は、{% ifversion ghes %}監査対象システム、{% endif %}ユーザ、Organization、リポジトリのイベントのログを保持します。 ログはデバッグや内部および外部のコンプライアンスに役立ちます。' +title: Audit logging +intro: '{% data variables.product.product_name %} keeps logs of audited{% ifversion ghes %} system,{% endif %} user, organization, and repository events. Logs are useful for debugging and internal and external compliance.' redirect_from: - - /enterprise/admin/articles/audit-logging/ + - /enterprise/admin/articles/audit-logging - /enterprise/admin/installation/audit-logging - /enterprise/admin/user-management/audit-logging - /admin/user-management/audit-logging @@ -16,31 +16,30 @@ topics: - Logging - Security --- +For a full list, see "[Audited actions](/admin/user-management/audited-actions)." For more information on finding a particular action, see "[Searching the audit log](/admin/user-management/searching-the-audit-log)." -完全なリストについては、「[監査済みのアクション](/admin/user-management/audited-actions)」を参照してください。 特定のアクションを見つける方法について詳しくは、「[Audit log を検索する](/admin/user-management/searching-the-audit-log)」を参照してください。 +## Push logs -## プッシュのログ - -Git プッシュ操作はすべてログに記録されます。 詳しい情報については、「[プッシュログを表示する](/admin/user-management/viewing-push-logs)」を参照してください。 +Every Git push operation is logged. For more information, see "[Viewing push logs](/admin/user-management/viewing-push-logs)." {% ifversion ghes %} -## システムイベント +## System events -すべてのプッシュとプルを含む監査されたすべてのシステムイベントは、`/var/log/github/audit.log` に記録されます。 ログは 24 時間ごとに自動的に交換され、7 日間保持されます。 +All audited system events, including all pushes and pulls, are logged to `/var/log/github/audit.log`. Logs are automatically rotated every 24 hours and are retained for seven days. -Support Bundle にはシステムログが含まれています。 詳しい情報については、「[{% data variables.product.prodname_dotcom %} Support にデータを提供する](/admin/enterprise-support/providing-data-to-github-support)」を参照してください。 +The support bundle includes system logs. For more information, see "[Providing data to {% data variables.product.prodname_dotcom %} Support](/admin/enterprise-support/providing-data-to-github-support)." -## Support Bundle +## Support bundles -すべての監査情報は、Support Bundle の `github-logs` ディレクトリにある `audit.log` ファイルに記録されます。 ログの転送が有効な場合、[Splunk](http://www.splunk.com/) や [Logstash](http://logstash.net/) などの外部の syslog ストリーミングコンシューマに、このデータをストリーミングすることができます。 このログからのすべてのエントリは、`github_audit` キーワードでフィルタリングできます。 詳しい情報については、「[ログの転送](/admin/user-management/log-forwarding)」を参照してください。 +All audit information is logged to the `audit.log` file in the `github-logs` directory of any support bundle. If log forwarding is enabled, you can stream this data to an external syslog stream consumer such as [Splunk](http://www.splunk.com/) or [Logstash](http://logstash.net/). All entries from this log use and can be filtered with the `github_audit` keyword. For more information see "[Log forwarding](/admin/user-management/log-forwarding)." -たとえば、次のエントリは新規リポジトリが作成されたことを示しています。 +For example, this entry shows that a new repository was created. ``` Oct 26 01:42:08 github-ent github_audit: {:created_at=>1351215728326, :actor_ip=>"10.0.0.51", :data=>{}, :user=>"some-user", :repo=>"some-user/some-repository", :actor=>"some-user", :actor_id=>2, :user_id=>2, :action=>"repo.create", :repo_id=>1, :from=>"repositories#create"} ``` -次の例は、コミットがリポジトリにプッシュされたことを示しています。 +This example shows that commits were pushed to a repository. ``` Oct 26 02:19:31 github-ent github_audit: { "pid":22860, "ppid":22859, "program":"receive-pack", "git_dir":"/data/repositories/some-user/some-repository.git", "hostname":"github-ent", "pusher":"some-user", "real_ip":"10.0.0.51", "user_agent":"git/1.7.10.4", "repo_id":1, "repo_name":"some-user/some-repository", "transaction_id":"b031b7dc7043c87323a75f7a92092ef1456e5fbaef995c68", "frontend_ppid":1, "repo_public":true, "user_name":"some-user", "user_login":"some-user", "frontend_pid":18238, "frontend":"github-ent", "user_email":"some-user@github.example.com", "user_id":2, "pgroup":"github-ent_22860", "status":"post_receive_hook", "features":" report-status side-band-64k", "received_objects":3, "receive_pack_size":243, "non_fast_forward":false, "current_ref":"refs/heads/main" } diff --git a/translations/ja-JP/content/admin/user-management/monitoring-activity-in-your-enterprise/audited-actions.md b/translations/ja-JP/content/admin/user-management/monitoring-activity-in-your-enterprise/audited-actions.md index 2c57090629a1..87a3c98508b3 100644 --- a/translations/ja-JP/content/admin/user-management/monitoring-activity-in-your-enterprise/audited-actions.md +++ b/translations/ja-JP/content/admin/user-management/monitoring-activity-in-your-enterprise/audited-actions.md @@ -3,7 +3,7 @@ title: Audited actions intro: You can search the audit log for a wide variety of actions. miniTocMaxHeadingLevel: 3 redirect_from: - - /enterprise/admin/articles/audited-actions/ + - /enterprise/admin/articles/audited-actions - /enterprise/admin/installation/audited-actions - /enterprise/admin/user-management/audited-actions - /admin/user-management/audited-actions diff --git a/translations/ja-JP/content/admin/user-management/monitoring-activity-in-your-enterprise/searching-the-audit-log.md b/translations/ja-JP/content/admin/user-management/monitoring-activity-in-your-enterprise/searching-the-audit-log.md index 173f2c3a91f4..9fc020f88aef 100644 --- a/translations/ja-JP/content/admin/user-management/monitoring-activity-in-your-enterprise/searching-the-audit-log.md +++ b/translations/ja-JP/content/admin/user-management/monitoring-activity-in-your-enterprise/searching-the-audit-log.md @@ -1,8 +1,8 @@ --- -title: Audit log を検索する -intro: サイト管理者は、Enterprise で監査されたアクションの広範なリストを検索できます。 +title: Searching the audit log +intro: Site administrators can search an extensive list of audited actions on the enterprise. redirect_from: - - /enterprise/admin/articles/searching-the-audit-log/ + - /enterprise/admin/articles/searching-the-audit-log - /enterprise/admin/installation/searching-the-audit-log - /enterprise/admin/user-management/searching-the-audit-log - /admin/user-management/searching-the-audit-log @@ -15,37 +15,37 @@ topics: - Enterprise - Logging --- - -## 検索クエリの構文 - -AND/ORの論理演算子で区切られた値のペア:1つ以上のキーを使って、検索クエリを構成します。 - -| キー | 値 | -| --------------:| --------------------------------------- | -| `actor_id` | アクションを開始したユーザアカウントの ID | -| `actor` | アクションを開始したユーザアカウントの名前 | -| `oauth_app_id` | アクションに関連付けられている OAuth アプリケーションの ID | -| `action` | 監査されたアクションの名前 | -| `user_id` | アクションによって影響を受けたユーザの ID | -| `ユーザ` | アクションによって影響を受けたユーザの名前 | -| `repo_id` | アクションによって影響を受けたリポジトリの ID （妥当な場合） | -| `repo` | アクションによって影響を受けたリポジトリの名前 （妥当な場合） | -| `actor_ip` | アクション元の IP アドレス | -| `created_at` | アクションが作成された時間 | -| `from` | アクション元の View | -| `note` | イベント固有の他の情報（プレーンテキストまたは JSON フォーマット） | -| `org` | アクションによって影響を受けたOrganizationの名前（該当する場合） | -| `org_id` | アクションによって影響を受けたOrganizationの ID（該当する場合） | - -たとえば、2017 年の初めからリポジトリ `octocat/Spoon-Knife` に影響を与えたすべてのアクションを確認するには、次のようにします: +## Search query syntax + +Compose a search query from one or more key:value pairs separated by AND/OR logical operators. + +Key | Value +--------------:| -------------------------------------------------------- +`actor_id` | ID of the user account that initiated the action +`actor` | Name of the user account that initiated the action +`oauth_app_id` | ID of the OAuth application associated with the action +`action` | Name of the audited action +`user_id` | ID of the user affected by the action +`user` | Name of the user affected by the action +`repo_id` | ID of the repository affected by the action (if applicable) +`repo` | Name of the repository affected by the action (if applicable) +`actor_ip` | IP address from which the action was initiated +`created_at` | Time at which the action occurred +`from` | View from which the action was initiated +`note` | Miscellaneous event-specific information (in either plain text or JSON format) +`org` | Name of the organization affected by the action (if applicable) +`org_id` | ID of the organization affected by the action (if applicable) + +For example, to see all actions that have affected the repository `octocat/Spoon-Knife` since the beginning of 2017: `repo:"octocat/Spoon-Knife" AND created_at:[2017-01-01 TO *]` -アクションの完全なリストについては、「[監査済みのアクション](/admin/user-management/audited-actions)」を参照してください。 +For a full list of actions, see "[Audited actions](/admin/user-management/audited-actions)." -## Audit log を検索する +## Searching the audit log {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.audit-log-tab %} -4. 検索クエリを入力します。![検索クエリ](/assets/images/enterprise/site-admin-settings/search-query.png) +4. Type a search query. +![Search query](/assets/images/enterprise/site-admin-settings/search-query.png) diff --git a/translations/ja-JP/content/admin/user-management/monitoring-activity-in-your-enterprise/viewing-push-logs.md b/translations/ja-JP/content/admin/user-management/monitoring-activity-in-your-enterprise/viewing-push-logs.md index d05e5c712b72..5f6e5fb0891c 100644 --- a/translations/ja-JP/content/admin/user-management/monitoring-activity-in-your-enterprise/viewing-push-logs.md +++ b/translations/ja-JP/content/admin/user-management/monitoring-activity-in-your-enterprise/viewing-push-logs.md @@ -1,8 +1,8 @@ --- -title: プッシュログの表示 -intro: サイト管理者は、Enterprise 上の任意のリポジトリに対する Git プッシュ操作の一覧を確認することができます。 +title: Viewing push logs +intro: Site administrators can view a list of Git push operations for any repository on the enterprise. redirect_from: - - /enterprise/admin/articles/viewing-push-logs/ + - /enterprise/admin/articles/viewing-push-logs - /enterprise/admin/installation/viewing-push-logs - /enterprise/admin/user-management/viewing-push-logs - /admin/user-management/viewing-push-logs @@ -16,31 +16,32 @@ topics: - Git - Logging --- +Push log entries show: -プッシュログの項目には次の情報が含まれています。 +- Who initiated the push +- Whether it was a force push or not +- The branch someone pushed to +- The protocol used to push +- The originating IP address +- The Git client used to push +- The SHA hashes from before and after the operation -- プッシュを開始した人 -- フォースプッシュであったかどうか -- プッシュされたブランチ -- プッシュするために使ったプロトコル -- プッシュ元の IP アドレス -- プッシュするために使った Git クライアント -- 操作前と操作後の SHA ハッシュ +## Viewing a repository's push logs -## リポジトリのプッシュログを表示する - -1. サイト管理者として {% data variables.product.prodname_ghe_server %} にサインインします。 -1. リポジトリにアクセスします。 -1. In the upper-right corner of the repository's page, click {% octicon "rocket" aria-label="The rocket ship" %}. ![サイトアドミン設定にアクセスするための宇宙船のアイコン](/assets/images/enterprise/site-admin-settings/access-new-settings.png) +1. Sign into {% data variables.product.prodname_ghe_server %} as a site administrator. +1. Navigate to a repository. +1. In the upper-right corner of the repository's page, click {% octicon "rocket" aria-label="The rocket ship" %}. + ![Rocketship icon for accessing site admin settings](/assets/images/enterprise/site-admin-settings/access-new-settings.png) {% data reusables.enterprise_site_admin_settings.security-tab %} -4. 左のサイドバーで、**Push Log（プッシュログ）** をクリックしてください。 ![プッシュログのタブ](/assets/images/enterprise/site-admin-settings/push-log-tab.png) +4. In the left sidebar, click **Push Log**. +![Push log tab](/assets/images/enterprise/site-admin-settings/push-log-tab.png) {% ifversion ghes %} -## コマンドラインでリポジトリのプッシュログを表示する +## Viewing a repository's push logs on the command-line {% data reusables.enterprise_installation.ssh-into-instance %} -1. 適切な Git リポジトリで Audit log ファイルを開いてください。 +1. In the appropriate Git repository, open the audit log file: ```shell - ghe-repo コードオーナー/リポジトリ -c "less audit_log" + ghe-repo owner/repository -c "less audit_log" ``` {% endif %} diff --git a/translations/log/ja-resets.csv b/translations/log/ja-resets.csv index aa71b33c4844..ae2e5260d8f5 100644 --- a/translations/log/ja-resets.csv +++ b/translations/log/ja-resets.csv @@ -156,6 +156,9 @@ translations/ja-JP/content/admin/advanced-security/enabling-github-advanced-secu translations/ja-JP/content/admin/advanced-security/viewing-your-github-advanced-security-usage.md,Listed in localization-support#489 translations/ja-JP/content/admin/advanced-security/viewing-your-github-advanced-security-usage.md,parsing error translations/ja-JP/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/allowing-built-in-authentication-for-users-outside-your-identity-provider.md,rendering error +translations/ja-JP/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/disabling-unauthenticated-sign-ups.md,rendering error +translations/ja-JP/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/index.md,rendering error +translations/ja-JP/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/using-cas.md,rendering error translations/ja-JP/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/using-ldap.md,rendering error translations/ja-JP/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/using-saml.md,rendering error translations/ja-JP/content/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad.md,rendering error @@ -166,6 +169,14 @@ translations/ja-JP/content/admin/authentication/managing-identity-and-access-for translations/ja-JP/content/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise.md,rendering error translations/ja-JP/content/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-user-provisioning-for-your-enterprise.md,rendering error translations/ja-JP/content/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users.md,rendering error +translations/ja-JP/content/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/index.md,rendering error +translations/ja-JP/content/admin/configuration/configuring-network-settings/configuring-a-hostname.md,rendering error +translations/ja-JP/content/admin/configuration/configuring-network-settings/configuring-an-outbound-web-proxy-server.md,rendering error +translations/ja-JP/content/admin/configuration/configuring-network-settings/configuring-built-in-firewall-rules.md,rendering error +translations/ja-JP/content/admin/configuration/configuring-network-settings/configuring-dns-nameservers.md,rendering error +translations/ja-JP/content/admin/configuration/configuring-network-settings/configuring-tls.md,rendering error +translations/ja-JP/content/admin/configuration/configuring-network-settings/enabling-subdomain-isolation.md,rendering error +translations/ja-JP/content/admin/configuration/configuring-network-settings/index.md,rendering error translations/ja-JP/content/admin/configuration/configuring-network-settings/network-ports.md,rendering error translations/ja-JP/content/admin/configuration/configuring-network-settings/using-github-enterprise-server-with-a-load-balancer.md,rendering error translations/ja-JP/content/admin/configuration/configuring-your-enterprise/accessing-the-administrative-shell-ssh.md,rendering error @@ -176,12 +187,15 @@ translations/ja-JP/content/admin/configuration/configuring-your-enterprise/confi translations/ja-JP/content/admin/configuration/configuring-your-enterprise/configuring-email-for-notifications.md,rendering error translations/ja-JP/content/admin/configuration/configuring-your-enterprise/configuring-github-pages-for-your-enterprise.md,rendering error translations/ja-JP/content/admin/configuration/configuring-your-enterprise/configuring-rate-limits.md,rendering error +translations/ja-JP/content/admin/configuration/configuring-your-enterprise/configuring-time-synchronization.md,rendering error translations/ja-JP/content/admin/configuration/configuring-your-enterprise/enabling-and-scheduling-maintenance-mode.md,rendering error +translations/ja-JP/content/admin/configuration/configuring-your-enterprise/enabling-private-mode.md,rendering error translations/ja-JP/content/admin/configuration/configuring-your-enterprise/index.md,rendering error translations/ja-JP/content/admin/configuration/configuring-your-enterprise/initializing-github-ae.md,rendering error translations/ja-JP/content/admin/configuration/configuring-your-enterprise/managing-github-mobile-for-your-enterprise.md,rendering error translations/ja-JP/content/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise.md,rendering error translations/ja-JP/content/admin/configuration/configuring-your-enterprise/site-admin-dashboard.md,rendering error +translations/ja-JP/content/admin/configuration/configuring-your-enterprise/troubleshooting-ssl-errors.md,rendering error translations/ja-JP/content/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise.md,rendering error translations/ja-JP/content/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud.md,rendering error translations/ja-JP/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-the-dependency-graph-and-dependabot-alerts-on-your-enterprise-account.md,rendering error @@ -256,20 +270,38 @@ translations/ja-JP/content/admin/policies/enforcing-policy-with-pre-receive-hook translations/ja-JP/content/admin/policies/enforcing-policy-with-pre-receive-hooks/creating-a-pre-receive-hook-script.md,rendering error translations/ja-JP/content/admin/policies/enforcing-policy-with-pre-receive-hooks/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance.md,Listed in localization-support#489 translations/ja-JP/content/admin/policies/enforcing-policy-with-pre-receive-hooks/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance.md,rendering error +translations/ja-JP/content/admin/user-management/index.md,rendering error translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise.md,rendering error +translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/adding-people-to-teams.md,rendering error translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/creating-teams.md,rendering error translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/index.md,rendering error +translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/managing-projects-using-jira.md,rendering error +translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/preventing-users-from-creating-organizations.md,rendering error translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/removing-organizations-from-your-enterprise.md,rendering error translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/streaming-the-audit-logs-for-organizations-in-your-enterprise-account.md,rendering error translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/viewing-the-audit-logs-for-organizations-in-your-enterprise.md,rendering error translations/ja-JP/content/admin/user-management/managing-repositories-in-your-enterprise/configuring-git-large-file-storage-for-your-enterprise.md,rendering error +translations/ja-JP/content/admin/user-management/managing-repositories-in-your-enterprise/disabling-git-ssh-access-on-your-enterprise.md,rendering error +translations/ja-JP/content/admin/user-management/managing-repositories-in-your-enterprise/troubleshooting-service-hooks.md,rendering error +translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/auditing-ssh-keys.md,rendering error +translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/auditing-users-across-your-enterprise.md,rendering error +translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/customizing-user-messages-for-your-enterprise.md,rendering error +translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/index.md,rendering error +translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/inviting-people-to-manage-your-enterprise.md,rendering error +translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/managing-dormant-users.md,rendering error translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/promoting-or-demoting-a-site-administrator.md,rendering error +translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/rebuilding-contributions-data.md,rendering error +translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise.md,rendering error translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/suspending-and-unsuspending-users.md,rendering error translations/ja-JP/content/admin/user-management/migrating-data-to-and-from-your-enterprise/about-migrations.md,rendering error translations/ja-JP/content/admin/user-management/migrating-data-to-and-from-your-enterprise/exporting-migration-data-from-githubcom.md,rendering error translations/ja-JP/content/admin/user-management/migrating-data-to-and-from-your-enterprise/exporting-migration-data-from-your-enterprise.md,rendering error translations/ja-JP/content/admin/user-management/migrating-data-to-and-from-your-enterprise/migrating-data-to-your-enterprise.md,rendering error +translations/ja-JP/content/admin/user-management/monitoring-activity-in-your-enterprise/activity-dashboard.md,rendering error +translations/ja-JP/content/admin/user-management/monitoring-activity-in-your-enterprise/audit-logging.md,rendering error translations/ja-JP/content/admin/user-management/monitoring-activity-in-your-enterprise/audited-actions.md,rendering error +translations/ja-JP/content/admin/user-management/monitoring-activity-in-your-enterprise/searching-the-audit-log.md,rendering error +translations/ja-JP/content/admin/user-management/monitoring-activity-in-your-enterprise/viewing-push-logs.md,rendering error translations/ja-JP/content/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on.md,rendering error translations/ja-JP/content/authentication/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on.md,rendering error translations/ja-JP/content/authentication/authenticating-with-saml-single-sign-on/authorizing-an-ssh-key-for-use-with-saml-single-sign-on.md,rendering error