> 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/enterprise/keeper-gateway/keeper-gateway-1.9.0.md).

# KeeperPAM Gateway 1.9.0

Released on Nov 11, 2026

**Overview**

KeeperPAM Gateway 1.9.0 is a major release introducing Native RDP and SSH Proxy, temporary AWS credentials for programmatic access, Wiz standing privilege removal, and Azure Managed Identity support. It expands KeeperDB with DynamoDB and SQL Server dynamic port support, extends KeeperAI to Azure AI Foundry, broadens Discovery and rotation coverage, and delivers significant security hardening along with major stability fixes for sessions, JIT, auto-update, and Gateway reconnection.

**New Features:**

* **Native RDP and SSH Proxy** - connect to RDP and SSH resources through native clients via the Gateway, with JIT and custom credential override support for tunnels.
* **Temporary AWS credentials** - the Gateway generates and delivers short-lived credentials for programmatic access to AWS.
* **Wiz (CNAPP) integration** - remove standing privilege for identities flagged by Wiz.
* **Ephemeral access to PAM cloud resources** - launch a connection with an ephemeral account after approval, with automatic login to the session.
* **Azure Managed Identity** - the Gateway auto-detects Azure Managed Identity on Azure-hosted infrastructure, removing the App Registration requirement. Also supported for Universal Secrets Sync.
* **Universal Secrets Sync (USS)** - sync Keeper records to GitHub Actions secrets, and skip duplicate cloud secret names instead of aborting the sync.
* **KeeperDB** - DynamoDB support, SQL Server dynamic TCP ports via SQL Browser, MongoDB SSL and advanced options, and legacy Entra ROPC and manual token entry.
* **KeeperAI on Azure AI Foundry** - threat detection supports OpenAI Responses API and Anthropic-compatible Azure AI Foundry endpoints.
* **Kerberos authentication** - support for Kerberos and the Protected Users group.
* **Discovery and rotation coverage** - SCOM and DCOM user service discovery and rotation, FreeIPA (Red Hat IdM) domain support, alternative login names, and option to clear lockout and enable users during rotation.
* **Security hardening** - KeeperAI, Gateway entrypoint, TLS verification, and bundled crypto library remediations.
* **Significant stability and performance upgrades**

**Improvements**

* **DR-952**: Discover and allow an alternative login name
* **DR-1152**: KDNRM custom field to force a script to run on the Gateway
* **DR-1166**: Commander commands accept a PAM Configuration UID
* **DR-1182**: SaaS rotation updated to use the new SaaS configuration record
* **DR-1219**: Option to clear lockout and enable users during rotation
* **DR-1220**: Sync Keeper records to secrets in GitHub Actions workflows
* **DR-1247**: Launch a connection to a PAM cloud resource with an ephemeral account after approval
* **DR-1254**: User is logged in automatically when launching a PAM cloud resource session
* **DR-1264**: USS skips and reports duplicate cloud secret names instead of aborting the sync
* **DR-1278**: Auto-detect Azure Managed Identity on Azure-hosted infrastructure, removing the App Registration requirement
* **DR-1311**: USS supports Azure Managed Identity to sync secrets
* **DR-1324**: Gateway generates temporary credentials for programmatic access to AWS
* **DR-1325**: Deliver and use temporary credentials for programmatic access to AWS
* **DR-1329**: Support FreeIPA (Red Hat IdM) with Domain Configuration
* **DR-1337**: Add DCOM to user service discovery and rotation
* **DR-1339**: Add SCOM to user service discovery and rotation
* **DR-1344**: Remove standing privilege for CNAPP provider Wiz
* **DR-1347**: JIT support for AD groups on machines
* **DR-1389**: Switch LDAP library from ldap3 to python-ldap
* **DR-1396**: Replace map-python with subprocess calls
* **DR-1417**: Update snowflake dependency to >=5
* **DU-765**: PAM Azure Configuration fields changed from required to optional
* **DU-777**: Removed Base URL from the pamGitHubConfiguration record type
* **PG-220**: Remediated EOL OpenSSL 1.1.1k bundled in the Linux binary
* **PG-352**: Support for Kerberos and the Protected Users group
* **PG-400**: Gateway entrypoint hardening for package, log level, and guacd environment handling
* **PG-403**: Support for new serve OAuth parameters
* **PG-407**: KeeperDB support for DynamoDB connections
* **PG-408**: KeeperDB forwards SSL mode, advanced options, and hosts for MongoDB sessions
* **PG-421**: Gateway control channel now verifies the Router TLS certificate
* **PG-426**: New entra-id-info Gateway action and fixed Azure configuration field label resolution
* **PG-437**: Transparent RDP Proxy
* **PG-438**: KeeperDB Proxy supports SQL Server dynamic TCP ports via SQL Browser instance name resolution
* **PG-439**: KeeperDB support for legacy Entra ROPC and manual token entry
* **PG-449**: KeeperRDP Proxy supports JIT and custom credential override for tunnels
* **PG-458**: Transparent SSH Proxy
* **PG-463**: KeeperAI support for OpenAI Responses API on Azure AI Foundry deployments
* **PG-470**: KeeperAI threat detection supports Anthropic-compatible Azure AI Foundry endpoints
* **PG-491**: RDP redirected drive renamed to “Keeper Drive” in Windows Explorer
* **PG-500**: New environment variable KEEPER\_GATEWAY\_JIT\_ELEVATION\_LOGIN\_DELAY\_SECS to delay login after JIT elevation
* **PG-504**: KDNRM notes logged when JIT cleanup succeeds with items left behind
* **PG-510**: Removed bundled CA trust for roots behind the compromised eMudhra intermediates (CVE-2026-114406)
* **PG-520**: Gateway trusts CA\_CERTIFICATES and supports install --base-url for self-hosted mirrors

**Bug Fixes**

* **DR-1158**: Issue where SaaS rotation failed for Cisco IOS XE
* **DR-1161**: Issue where pamHostname port was created as an integer instead of a string
* **DR-1171**: Issue where generated IAM passwords did not contain a symbol
* **DR-1314**: Issue where the Gateway dropped serverPublicKey from the persisted KSM config, breaking IL5 dynamic-key one-time tokens
* **DR-1335**: Issue where JIT did not handle errors during cleanup
* **DR-1345**: Issue where Discovery crashed when a worker thread was abandoned
* **DR-1346**: Issue where a port scan timed out at 120 seconds but the Discovery job reported Completed with incomplete results
* **DR-1365**: Issue where Azure Client Secret SaaS rotation deleted the old secret before creating the replacement, which could leave the app with no secrets
* **DR-1393**: Issue where CNAPP AWS standing privilege removal failed when removing all groups and roles together
* **DR-1398**: Issue where Azure secret deletion during SaaS rotation was not retried
* **DR-1403**: Issue where LDAP rotation for FreeIPA did not set password expiration to a future time
* **DR-1405**: Issue where rotation reported a misleading “Administrative credentials missing” error when the user is not linked to the resource in the PAM Configuration
* **DR-1407**: Issue with the FreeIPA non-expiring password timestamp
* **DR-1409**: Issue where the pamDatabase “Verify SSL” setting was not applied during database rotation
* **DR-1411**: Issue where AWS IAM password rotation failed for IAM users whose name contains “@”
* **DR-1413**: Issue where SQL Server JIT cleanup dropped the database user but left the server login behind
* **DR-1416**: Issue where a missing SQL Server JIT elevation role caused a TypeError instead of a clear error
* **DR-1420**: Issue where MongoDB usernames and passwords were not escaped in the connection URI
* **DR-1424**: Issue where USS AWS secrets were not created when the record title contained characters invalid in AWS tag values
* **PG-218**: Issue where Windows RDP sessions failed after 5 to 10 minutes with session recording enabled
* **PG-349**: Issue where an RDP session kept running after being terminated from the Keeper connection tab
* **PG-358**: Issue where RDP drive redirection failed on Windows Gateways
* **PG-390**: Issue where Windows auto-update never ran because the scheduled task command path was not quoted
* **PG-391**: Issue where rotate-on-termination and session-end ARAM audit events did not fire
* **PG-398**: Issue where SSH session recordings were lost for ephemeral and elevated sessions on RHEL 8
* **PG-409**: Issue where RDP drive redirection failed in Docker Compose deployments with volume mounts
* **PG-425**: Issue where PostgreSQL Launch Credential connections failed due to a protocol naming mismatch
* **PG-427**: Issue where resources leaked when connections closed early
* **PG-428**: Issue where KeeperDB Proxy query logging dropped queries on SQL Server with SSMS
* **PG-429**: Issue where restricted guacd parameters were not matched correctly
* **PG-446**: Issue where “Connection Open” events were reported twice
* **PG-453**: Issue where Windows auto-update turned itself off after one update
* **PG-456**: Issue where closing the last KeeperDB session stopped the Gateway and dropped all other sessions
* **PG-457**: Issue where rotation failures showed “object has no attribute ‘strip’” instead of the actual error
* **PG-459**: Issue where DynamoDB ConnectAs launches dropped the STS session token
* **PG-461**: Issue where the Gateway disconnected when a long-running action such as a JIT group add blocked for 15+ seconds
* **PG-464**: Issue where the Linux Gateway failed to start on EL9 (AlmaLinux 9) due to a missing libcrypt dependency
* **PG-468**: Issue where JIT teardown blocked new sessions and ran cleanups in the wrong order
* **PG-469**: Issue where JIT accounts and group memberships were not cleaned up when session start failed after provisioning
* **PG-476**: Issue where concurrent sessions on Windows Gateways failed while the embedded guacd was starting
* **PG-478**: Issue where a failed session start caused later recorded sessions on the Gateway to fail until restart
* **PG-479**: Issue where the Gateway leaked UDP sockets after each WebRTC session
* **PG-483**: Issue where rotation ignored password complexity when the stored value was unpadded base64
* **PG-488**: Issue where the Gateway stayed offline after its first Router WebSocket handshake failed
* **PG-492**: Issue where the Gateway stopped reconnecting for 6 hours after a 429 response and reconnected in lockstep after a mass disconnect
* **PG-495**: Issue where RBI autofill used the passkey username instead of the record’s Login field
* **PG-497**: Issue where JIT named account elevation failed due to AD replication timing
* **PG-498**: Issue where KeeperDB launch failed with a generic error when the cache directory was not writable
* **PG-505**: Issue with proxy tunnel settings handlers after the protocol change
* **PG-509**: Issue where the RBI browser did not start on FIPS hosts with a kernel older than 5.6 (Gateway now warns at startup)
* **PG-516**: Issue where KeeperRDP Proxy could not connect to targets that only allow Standard RDP Security

Please visit the KeeperPAM Gateway documentation for your specific platform:

{% content-ref url="/spaces/-MJXOXEifAmpyvNVL1to/pages/YVitXRsJWzo14VlLdwoR" %}
[Gateways](https://docs.keeper.io/keeperpam/privileged-access-manager/getting-started/gateways.md)
{% endcontent-ref %}


---

# 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/enterprise/keeper-gateway/keeper-gateway-1.9.0.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.
