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.2 is Available

We are excited to announce the release of a new MuseKnowledge™ Proxy version 5.2, which is now available for download, trial and purchase/upgrade.

MuseKnowledge™ Proxy Version 5.2 brings significant features and improvements to support easier, faster setup and administration of MuseKnowledge™ Proxy in Self-Hosted environments. The detailed list of changes is available in MuseKnowledge™ Proxy Release Notes PDF Document.

Added SIP (Session Initiation Protocol, version 2.0) authentication module. Both Telnet and TCP/IP layers are supported.

POP authentication Login module is now available for legacy setups to authenticate users through the Post Office Protocol. It is recommended to use this module only with self-managed email services (on-premise) and not with global email providers, where SSO / SAML is actually encouraged.

For uniformity, LOG_USER_ID, LOG_USER_ID_MODE and USED_PARAMS configuration entries can now be read and interpreted by more of the direct login modules: U/P, FTP, SIP, IMAP,POP.

The Muse Proxy cookies were enhanced with a second cookie that is sent on plain http:// and cast without the SameSite=None attribute. All these were implemented to address the Chrome browser changes with regard to the cookie cross-domain standards and the introduction of the requirement for SameSite=None; Secure attributes.

First steps on implementing localization were done, including support for localizing the server messages and also messages reported by configured login modules. The LOCALE element was added globally in MuseProxy.xml configuration file, but can also be configured at the application level in ${APPLICATION_HOME}/WEB-INF/web.xml configuration file or, for some login modules, which support the SCRIPT Post-authentication logic, via the special variable locale; there is also some support for using the locale= parameter for the application actions to some extent – specifying an explicit locale parameter while login means the whole session will use it, while specifying for a certain action means direct errors will be yielded in that language (although the source navigation will use the session locale).

Muse Proxy Application expiry test logic was modified in order to benefit from the specific web.xml application locale and possibly use the application customized expiry key.

The cyclic refresh is now skipping the Shortcut Mappings update for the expired applications.

The following new optional entries are available for the authentication process in the ${WEB_CONTEXT_HOME}/profiles/AuthenticationGroups.xml configuration file:

A Pre-authentication module is available to interpret a set of rules which ensures that the configured login modules are called only if the request is successfully validated against those rules. This can limit the number of login requests against the back-end services for black-listed user names, because only valid requests will reach the login module.
For a chain of sufficient login modules, an explicit sources group identifier can be set per login module using the SOURCES_GROUP_ID entry under AUTHENTICATION_GROUPS/AUTHENTICATION_GROUP/AUTHENTICATIONS/AUTHENTICATION, and this value will be used if the successfully authenticated login module doesn’t provide another value for source group identifier via its own configuration module.
Similarly, the PROXY_HOST and PROXY_PORT configurations located inside of AUTHENTICATION_GROUPS/AUTHENTICATION_GROUP/AUTHENTICATIONS/AUTHENTICATION can be used as default values if the successfully authenticated login module doesn’t provide another values via its own configuration module.

Changes were made in order to make sure that the Navigation Manager will relay the Server Sent Events, a standard which is now part of HTML5. However, no filtering support is currently available for this type of request.

In the Administrator Console, Manage Applications area, the speed of extracting details for all the configured applications was improved; loading hundreds of applications offers now a better experience, especially on multi-core CPUs installations.

Creating authentication groups from scratch is a new feature added in Administrator Console / Manage Applications area.

The Add New Source feature is available in Administrator Console / Manage Applications to provide support to create and add a new source from scratch based on the usual frequent fields.

Starting with this version, the DEF configuration entry from an existent source profile can be visually edited from Administrator Console / Manage Applications.

In Manage Applications section from the Administrator Console it is now possible to visually manage the users defined in the ${WEB_CONTEXT_HOME}/profiles/login/ProxyLoginModuleUserPassword.xml configuration file of an application. The following actions can be done through the admin web interface: manage the file groups, add a new user, edit a user, delete selected users, import users from a CSV file and export selected users as a CSV file.

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