> 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/developer-tools/commander/commander-17.1.7.md).

# コマンダー 17.1.7

2025年8月28日リリース

## 修正と向上点

* `import` コマンド: [CyberArkユーザーポータルからのインポート](/keeperpam/jp/commander-cli/command-reference/import-and-export-commands/cyberark-import.md)に対応。
* `audit-alert` コマンド: `--all` パラメータでアラートの一括有効化、無効化が可能に。
* `pam rotation edit` コマンド: バグ修正。
* `one-time-share` コマンド: 編集可能な共有に対応。双方向ワンタイム共有について詳しくは[こちら](/enterprise-guide/jp/sharing/one-time-share.md#wantaimu)のページをご参照ください。
* コマンダー `service mode`: 複数スレッドや長時間処理を扱うためのリクエストキューに対応したAPIバージョン2を追加。サービスモードについて詳しくは[こちら](/keeperpam/jp/commander-cli/service-mode-rest-api.md)のページをご参照ください。

#### アップグレードに関する注意

コマンダーサービスモードをご利用のお客様向けに、このアップデートでは新しいサービスがデフォルトでV2 API (キュー方式のシステム) を使用するようになります。V1 APIを使用する場合は、キューシステムを有効にするか確認された際に「n」を選択してください。

**変更履歴は**[**こちら**](https://github.com/Keeper-Security/Commander/compare/v17.1.6...v17.1.7)**をご参照ください。**

## 関連リンク

* [コマンダードキュメント](/keeperpam/jp/commander-cli/overview.md)
* [リリースバイナリ](https://github.com/Keeper-Security/Commander/releases)
* [開発者用セットアップ](/keeperpam/jp/commander-cli/commander-installation-setup.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/developer-tools/commander/commander-17.1.7.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.
