Products
- Muse^® Federated Search, today’s most powerful of its kind, is known as best of multiple target searching and content normalization to a single data model.
- Muse^® Proxy is a highly customizable multi-platform proxy server, easy to use and manage, acting as a gateway to authenticated content.
- Muse^® Harvest is based on different types of controlled extraction, such as search, date or feed based. it features a consistent delivery record format.
  - Overview
  - Features
- Muse^® Hybrid brings a powerful new approach to content discovery by combining real-time global federated searching with high performance central indexed searching.
  - Overview
  - Features
Services
Support
- FAQ
- Downloads
About
Contact

MuseKnowledge™ Proxy 5.3 is Available

A new version of MuseKnowledge™ Proxy was released and it is available for trial, purchase or upgrade. The highlights of the new version are presented below. The detailed list of changes is available in MuseKnowledge™ Proxy Release Notes PDF Document.

An Audit Report can now be generated using the MuseKnowledge Administrator Console, Manage Applications section for the current selection of applications. The report includes a cumulative section, individual application details, and Source Profiles details.
Testing and managing the Authentication for LDAP Configuration in the MuseKnowledge Administrator Console is now possible. In order to ease the LDAP authentication configuration visual management and step by step tests are available. Check Network Parameters, Check Root (Bind) Authentication, discovering Search Bases, searching for the user (or any Search String), entirely testing the whole chain with a User and Password are now possible in an intuitive manner from the same screen allowing visual edit. Raw edit is still available.
The Priority cookie attribute is now set to MuseKnowledge Proxy Session and ID cookies. This attribute is interpreted by Chrome, Microsoft Edge and other Chromium based browsers, while the others are ignoring it. This way, in case the per domain cookie capacity (usually 180 cookies) exceeds on the end-user browser side, the proxy session cookie is not evicted hence the session could still be maintained. This is configurable through the priority="High" XML attribute of the PRIMARY_COOKIE_CONFIG and SECONDARY_COOKIE_CONFIG elements in the MuseProxy.xml configuration file. Note that these two settings, PRIMARY_COOKIE_CONFIG and SECONDARY_COOKIE_CONFIG, are overwritten when upgrading, so the customized bits need to be manually reverted.
In this release the JavaScript libraries involved in the default application interface templates (MKPF and MuseProxyFoundation), in the static pages and in the MuseKnowledge Administration Console were updated to newer versions.
Expired link corresponding to applications with indirect authentication (SAML, SSO, RemoteAuth) are not triggering the login flow if the HTTP request headers Purpose: prefetch or Sec-Purpose: prefetch are present.
A Request Timeout for reading the entire HTTP request is now available in the MuseProxy.xml configuration file. Note that it must be significantly higher than the KEEP_ALIVE_INTERVAL and READ_TIMEOUT value. In case a load balancer or a reverse proxy is used in front of the MuseKnowledge Proxy they normally take care of this aspect.
The logUserID is now available in the Application FreeMarker model and can be accessed through session.getLogUserID() in the FreeMarker templates, in cases of applications which may have clear human readable userIDs and no displayName is available in the post-authentication properties or the authentication module does not have such properties.
The debug log now adds more information about client connection, especially on some client side errors so that the client / peer IP (end-user / load-balancer IP in case the end-user IP is not encoded by the load balancer) is also part of the same log entry without the need to identify it in previous entries or in entries from other log files. For the vendor side of connection efforts were made so that the source.ip and target.hostPort are logged in the same error entry for some errors. The client.ip, source.ip and target.hostPort information is, however, not duplicated for each log entry with a [connection.id=...]. Hints about HTTP Tunnel connections are now present.

To support libraries during COVID-19 global crisis, MuseKnowledge™ Proxy Trial periods are now extended from 30 days to 90 days. Request your Trial License Key by simply filling in the trial form.

Back to News