> For the complete documentation index, see [llms.txt](https://docs.keeper.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.keeper.io/release-notes/jp/enterprise/keeper-gateway/keeper-gateway-1.8.8.md).

# Keeperゲートウェイ 1.8.8

2026年8月14日リリース

## 概要 <a href="#overview" id="overview"></a>

Keeperゲートウェイ 1.8.8では、サービスアカウント依存関係を手動設定できる機能を追加し、connect-as起動、大規模Active Directory環境におけるJIT特権昇格、KeeperDBの認証情報選択に関する不具合に対応しました。

## 改善点 <a href="#improvements" id="improvements"></a>

* **PG-367:** サービスアカウント依存関係を手動設定できる機能に対応。

## バグ修正 <a href="#bugs" id="bugs"></a>

* **PG-365:** connect-as起動時にゲートウェイが `user.totp` を受信しない不具合を修正。
* **PG-345:** 大規模AD環境でグループをすべて列挙する処理によりJIT特権昇格がタイムアウトする不具合を修正。
* **PG-388:** 構成が設定されている場合に、KeeperDB起動時に選択または指定した認証情報が使用されない不具合を修正。

## アップデート手順 <a href="#update-instructions" id="update-instructions"></a>

ご利用のプラットフォームに応じた更新手順については、[こちら](/keeperpam/jp/privileged-access-manager/getting-started/gateways.md)のページをご参照ください。


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.keeper.io/release-notes/jp/enterprise/keeper-gateway/keeper-gateway-1.8.8.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.