# Commander 17.2.8

#### New Features

* Added --aging flag to compliance report with record aging data (created, last\_modified, last\_rotation, last\_pw\_change)
* Added --username and --team filters to all compliance subcommands
* Added --resolve-teams flag to sfr and team-report for expanding team filter to individual team members
* Added pam project extend command
* Added --keeper-db-proxy (-kdbp) flag to pam tunnel edit for pamDatabase records
* Added --launch-user (-lu) flag to pam connection edit for setting launch credentials
* Updated SaaS commands to use new saasConfiguration record type
* Added Enforcement and Managed Node Details to enterprise-info Roles output

#### Improvements

* Incremental compliance data sync with per-user staleness tracking to avoid full re-fetches on warm cache
* Per-user cache invalidation for filtered compliance reports — only stale users are fetched from the API
* Dynamic chunking with probe timeouts for preliminary compliance data fetching
* Client-side request timeouts to prevent indefinite hangs during compliance sync
* Enterprise and MSP command improvements

#### Bug Fixes

* Fixed trickle ICE handling for pam launch command
* Fixed lsf returning "No shared folders found" when no search string was provided
* Fixed cc and ls commands to restore regex search behavior
* Fixed invalid base64 handling
* Fixed ACL lookup skipping for configuration records (which have no parent)
* Prevented PAM records from being used in One-Time Shares
* Filtered false-positive record\_password\_change events in compliance report (first-set events discarded)

Full Changelog: [v17.2.7...v17.2.8](https://github.com/Keeper-Security/Commander/compare/v17.2.7...v17.2.8)


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.keeper.io/release-notes/developer-tools/commander/commander-17.2.8.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.