> For the complete documentation index, see [llms.txt](https://docs.ovaledge.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ovaledge.com/release8.1/hotfix-releases/release8.1.0.x/release8.1.0.5.md). # Release8.1.0.5 This release introduces enhancements and bug fixes across Model Context Protocol, Lineage, Data & Metadata Changes, and Jobs, improving enterprise authentication, audit visibility, lineage efficiency, metadata comparison accuracy, and job log accessibility. **Key Highlights** * **Model Context Protocol**: Added an Audit Log Export API for scheduled MCP access log retrieval and introduced OAuth 2.0 authentication support alongside existing authentication methods, enabling secure enterprise integrations with comprehensive audit visibility. * **Lineage**: Optimized QuickSight lineage processing to eliminate redundant analysis rebuilds for shared dashboards, improving build efficiency and lineage status reliability. * **Data & Metadata Changes**: Fixed incorrect data-type modifications in Redshift metadata comparisons, ensuring only actual schema changes are reported. * **Jobs**: Resolved job log download failures, ensuring logs are generated and downloaded successfully for analysis and troubleshooting. Release Details:
Release TypeRelease VersionBuild<Release. Build Number. Release Stamp>Build Date
Hotfix ReleaseRelease8.1.0.5release8.1.0.5.8105.c1270d9August 04, 2026
## Model Context Protocol ### New & Improved **Audit Log Export API for MCP Access Monitoring** There was no dedicated way to programmatically retrieve MCP API access logs for security monitoring. Organizations had limited options for identifying who accessed MCP endpoints, when requests were made, which parameters were passed, and the associated IP addresses or session details. With this enhancement, a new Audit Log Export API enables scheduled retrieval of MCP API access logs. The API provides details such as the user, the accessed endpoint, the request time, the request parameters, and IP or session information, allowing organizations to export and integrate audit logs with external monitoring systems. **OAuth 2.0 Authentication Support for OvalEdge MCP Server** The OvalEdge MCP Server supported API Key and Basic Authentication for authenticating MCP client requests. While effective, this required manual credential management and configuration, making enterprise onboarding and integration with modern AI platforms more complex. With this enhancement, the OvalEdge MCP Server now supports OAuth 2.0 authentication alongside the existing API Key and Basic Authentication methods. Administrators can configure the server to use API Key, OAuth, or a hybrid authentication mode based on deployment requirements. Existing role-based access controls, governance policies, permissions, and audit logging continue to be enforced after successful authentication. ## Lineage ### New & Improved **Improved QuickSight Lineage Building for Shared Analyses** Building lineage for QuickSight dashboards and analyses simultaneously led to redundant lineage processing and inconsistent build statuses. When the same analysis was shared across multiple dashboards, its lineage was rebuilt for each dashboard, increasing processing time and occasionally causing status mismatches. With this enhancement, the QuickSight lineage build process has been optimized to avoid unnecessary rebuilds of analysis lineage when analyses are shared across multiple dashboards. The updated process also improves lineage status handling during dashboard and analysis builds, resulting in more reliable execution. ## Data & Metadata Changes ### Fixed **Resolved False Data Type Changes in Redshift Metadata Comparison** In Data & Metadata Changes for the Redshift connector, an issue in which columns were incorrectly marked as modified due to differences in how data types are displayed has been resolved. Columns with the same data type were incorrectly shown as changed, even though no changes had been made in the source. The comparison logic has been updated to prevent false modification results when the data type remains unchanged. ## Jobs ### Fixed **Resolved Job Log Download Failure** In Jobs, an issue in which job log downloads stopped before completion and no file was generated has been resolved. The download process has been fixed to ensure job logs are downloaded successfully for analysis and troubleshooting. *** Copyright © 2026, OvalEdge LLC, Peachtree Corners, GA, USA. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.ovaledge.com/release8.1/hotfix-releases/release8.1.0.x/release8.1.0.5.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.