# Oracle Database support enters beta with new process-based identifiers

Aembit has released new versions of the following components and packages:

* Helm Chart
* VM Agent Proxy package
* VM Agent Controller package
* AWS Lambda Extension
* AWS Lambda Layer
* Agent Injector
* Agent Proxy
* Agent Controller

For the latest available versions of these components, see the [Edge Components Supported Versions](/reference/edge-components/edge-component-supported-versions) page.

Key Updates:

* Oracle Database protocol support (Limited Beta)
* Support Process Command Line and Process Path client workload identification

***

Aembit’s Agent Proxy now supports the **Oracle Database** application protocol in Limited Beta. This enables Aembit to manage access for client workloads connecting to Oracle databases by intercepting the TNS wire protocol and injecting credentials transparently.

**Key capabilities:**

* Username/password credential injection for Oracle 19c and 21c databases (12C password verifier only)
* Support for thin Oracle clients (Java, Python), with experimental thick client support
* Tested with AWS RDS for Oracle and containerized Oracle environments
* Transparent steering on Linux VM deployments

For setup instructions, see the [Oracle Database Server Workload guide](/user-guide/access-policies/server-workloads/guides/oracle-database). For an overview of how Oracle protocol support works, see [About Oracle Databases](/user-guide/deploy-install/databases/about-oracle-databases).

***

Aembit’s Agent Proxy now supports **Process Command Line** and **Process Path** as Client Workload identifiers. These identifiers allow you to identify client workloads based on their full command line or executable path, providing more granular control over which applications can access your protected resources.

**Key capabilities:**

* **Process Command Line**: Identify workloads by the full command used to start them, including arguments. Supports wildcard matching to target specific arguments (for example, `*--env production*`).
* **Process Path**: Identify workloads by the exact filesystem path of the executable.
* Combine with other identifiers like Process Name and Process User Name for precise matching.
* Supports Linux virtual machine deployments.

For configuration details, see [Process Command Line](/user-guide/access-policies/client-workloads/identification/process-command-line) and [Process Path](/user-guide/access-policies/client-workloads/identification/process-path).