MuseKnowledge™ Application 8.0

Following its development trail, the MuseKnowledge™ Application reached version 8.0, which brings all improvements and new functionalities that were implemented over the past 3 years.

Here are some of the new features of our flagship search application, grouped by their location.

Search Form:

  • Query Suggestion with type-ahead features. The suggestions are presented to the end-user as he is typing, at any moment the user can select any of them from the list and launch the search. The suggestions are driven from the set of queries used by all users of the Muse system.
    Query Suggestions
  • Spellcheck / "Did you mean" functionality for the end-user's query. After the end-user launches the search, if there are misspellings in the query, a corrected one is displayed below the search form with a "Did you mean:" label. Clicking on the suggested query will launch the search with the new terms. This feature is based on indexed dictionaries per language, with extended capabilities such as words family, e.g. singular, plural, infinitive, participles, past tense, and checks queries against common spellings of each word. In addition, it is possible to use as data source besides dictionaries, the entire set of queries used in the Muse system. This is most useful when specialized query terms are being used which are not found in dictionaries.
    Spellcheck from a single data source, e.g. dictionary
    Spellcheck from single data source
    Spellcheck from a two data sources, e.g. dictionary and user queries
    Spellcheck with multiple data sources
  • Translation of the query. When the language of the query entered into the search form is detected as being different than application's active interface language (or a different configured language), the query is translated at the end-user's disposal into the referred language so that it can be available for launching a new search. For example, while in the MuseKnowledge Search Application English interface and entering an Arabic query, the end-user is offered with the possibility of translating the Arabic query into English and to use the resulted translation for a new search.
    This is most useful for non-English end-user speakers while searching with non-English terms against resources that have content only in English and which usually retrieve no results. With this new feature they can search using the translated query, thus increasing the possibility of retrieving results.
    For example, if the current language of the Muse Search application interface is English, and the user enters an Arabic query (or a query in any other language than English), then the Query Translation functionality is offered for the English language:
    Query Translate
    and upon end-user action of clicking on the link, the translation appears:
    Query Translate
  • Speech to Text functionality feature allows users to insert text into the inputs of the application, like the main search form, just by speaking to a microphone. The spoken text is recognized and it is automatically written in the selected input. This feature is only available on desktop computers (not phones or tablets, which already have this native functionality) and for a small set of inputs, only the ones where users can enter free text, such as search, filtering or help terms.
  • Virtual Keyboard functionality which allows to input free text without the need of physical keys. It can be used to enter login credentials or search terms and has a layout for each language of the application interface.
    Virtual Keyboard

Home and Search Results Page:

  • Multiple widgets are available for the application's Home page to offer increased functionality for the end-users. All widgets are configurable, they can be enabled/disabled through the Muse Console for Applications Administration.
    • Titles A to Z. The lists with the subscribed titles (books and journals) are ingested into the Muse Central Index and made available for browsing and searches.
    • Publishers. The list of subscribed publishers and their products are nicely displayed in tiles with publisher logos and descriptions. Direct links are available to navigate to publisher platforms using the institutional customer subscription.
    • RSS feeds. A RSS feed can be configured to display items in a widget in the application's Home page.
    • Important Links. External links with accompanying descriptions can be configured into this widget.
    • New: Books and Journals. Static metadata displaying a list of subscribed journals/books to promote for the end-users.
    • Top 10 Most Accessed Titles. This widgets presents the top 10 most accessed titles from the Titles A to Z widget.
  • Implemented the possibility to switch between a Simpler interface view with light functionality and a Richer one with the most complete set of application features that were enabled. A default view (Simpler or Richer) can be set per each application, switching between the views can be done from the "Search Options" panel, "Display Options" section, "View Display" option.
  • "Refine your Results" extended its visual representation with vertical bars for the "Dates" faceting option. The filtering action can be triggered by clicking a specific vertical bar corresponding to the desired date value. Also a slider is available for narrowing the dates for filtering the current result set based on the selected interval. Furthermore, the "Dates" filtering options were enhanced with new values: "Last Month", "Last 6 Months", "Last Year.
    Date Facet
  • The records images are also displayed in a separate widget called Images. It is available in the main area, just after the results and pagination display. The new Images widget presents in an images carousel all images from all retrieved records, clicking on any image will open the image viewer where various actions can be performed, like zoom in/out, move, rotate and share on social networks.
    Images Widget
  • "My List" functionality, which allows to save selected results from multiple searches into a temporarily list for later handling. The results saved into "My List" are available for the current session and they can be used with the existing actions, such as email, saving them into various formats, etc.

Muse Console for Applications Administration (MCAA):

  • All application's new features are configurable through the Muse Administration Console. The application's look and feel can also be customized by writing custom HTML code for header, footer and login page, adding custom CSS. Images such as customer logos can be uploaded on the server and referred into the custom code.
  • The application's widgets can be arranged by drag and drop.
  • The main functionalities can be enabled/disabled per each display type, e.g Extra Small Devices, Small Devices, Medium Devices, Large Devices.

As usual we offer a Free 30 Day Trial period to fully evaluate the new version of MuseKnowledge™ Application. You can request a trial access by simply filling in the trial form.

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.

Configure the Muse Proxy service with NGINX front-end

NGINX is an HTTP and reverse proxy server that can be placed in front of web applications to achieve custom workflows and provide solutions where multiple web applications cannot co-exist with similar specifications.

Specifically the NGINX server can be configured as front-end for Muse Proxy when Muse Proxy cannot be configured to use the standard ports – 80 for HTTP and 443 for HTTPS access. Because there are other applications needing the standard ports as well. Only for this situation, when multiple web applications are hosted on the same server it is recommended to use NGINX, otherwise if Muse Proxy is the only hosted service, it must be accessed directly, without a front-end reverse proxy solution.

Hosting multiple web applications with NGINX as front-end reverse proxy requires assigning a dedicated fully qualified domain name (FQDN) for each application.

In this article we are describing the necessary configurations for NGINX and Muse Proxy only. It is assumed that NGINX and Muse Proxy are already installed, this article does not cover their installations.

Further assumptions:

  1. To exemplify, we consider the Muse Proxy assigned FQDN to be And the server IP – The server OS is a Linux distribution (Debian, Ubuntu, RedHat, CentOS, etc).
  2. Muse Proxy is configured with its default ports – 9797 for HTTP and 9443 for HTTPS
  3. The wildcard DNS record is enabled for the Muse Proxy assigned FQDN – *
  4. A wildcard SSL certificate is available, thus the certificate and the private key exist on the server. The certificate must contain as SAN entries both * and

Configure the Muse Proxy service with NGINX front-end

In the NGINX configuration file for the Muse Proxy FQDN (e.g. /etc/nginx/sites-available/ define the backend service:
upstream backend_proxy {

For each port (80 and 443) contexts make sure the server_name has both values, e.g. * and Sample entries:

server {
        listen 80;
        listen [::]:80;
        server_name *;
        location / {
                include proxy_params;
                proxy_pass http://backend_proxy;
                proxy_buffer_size 128k;
                proxy_buffers 4 256k;
                proxy_busy_buffers_size 256k;
server {
        server_name *;
        listen 443 ssl;
        ssl_certificate /etc/ssl/;
        ssl_certificate_key /etc/ssl/;
        location / {
                include proxy_params;
                proxy_pass http://backend_proxy;
                proxy_buffer_size 128k;
                proxy_buffers 4 256k;
                proxy_busy_buffers_size 256k;

The content of /etc/nginx/proxy_params refered in the above samples:

proxy_set_header Host $http_host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;

Increase the timeout value for NGINX in /etc/nginx/nginx.conf, e.g.:

proxy_read_timeout 600s;

The NGINX service must be reloaded to pick up the configuration changes.

Configurations for Muse Proxy

Some configurations are needed for Muse Proxy as well, in its main configuration file ${MUSE_HOME}/proxy/MuseProxy.xml:
Define the external ports of NGINX as follows:

<PORT enabled="true" external="80">9797</PORT>
<SSL_PORT enabled="true" external="443">9443</SSL_PORT>

Specify the allowed IPs (of the machine itself) that allowed to provide the X-FORWARDED-FOR header value:


Make sure the FQDN value is configured in the SERVER_NAMES field, e.g.:


Following its development trail, MuseKnowledge™ Proxy recently reached version 5.1 Build 02, version which is now available for download, trial and purchase/upgrade. The results of our work are briefly presented in this news item.

  • Source pages containing Internationalized Domain Names (IDN), instead of their ASCII can now be rewritten if the source profile contains a new configuration, TRY_IDN. So far MuseKnowledge Proxy was able to rewrite the ASCII equivalent (e.g. in a HTML page, but now it is possible to rewrite directly hrefs containing IDNs, for example <a href="http://www.româ">
  • In order to ease the management of SSL keys and certificates for proxies where SSL termination is not involved, we have created a new section, named Server KeyStores, in the MuseKnowledge Administrator Console.
  • A Library Card’s Barcode application authentication module is available using multiple pattern rules. NUM, NUMMOD10, CODE39 and CODE39MOD43 are the algorithms supported at this time for the barcode validation.
  • Continued the work on integration with LTI standard – starting with this version a MuseKnowledge Proxy system can be certified as being LTI Compliant as an external service tool consumer by IMS Global Learning Consortium. This version can pass all necessary certification tests for LTI 1.0 standard.
  • With the newer versions of web browsers implementing Intelligent Tracking Prevention (3rd party cookies) and this option being enabled by default more changes were performed in order to run in an iframe within the LMS systems (Canvas, for example).
  • For SAML authentication, the signing and digest method algorithms to be used in signing SAML messages and metadata can now be specified per tenant not just globally thus allowing both for the deprecated SHA1 and for the recommended SHA256 configuration to function in the same MuseKnowledge Proxy instance.
  • Type 1 URL’s originating from a MuseKnowledge Search application are signed with a HMAC signature. The MuseKnowledge Search application(s) that connects to this new version of Muse Knowledge Proxy must be updated to use modulesutil.jar version 1.2338 or higher.
  • This version is introducing the Usage Limits component in order to limit against automated process or abusive users. Though available, it is recommended to use this component only for isolated cases because the current de-facto standard of web applications implies dozens of requests and big JavaScript code just to reach, for example, a journal issue. If lower limits are set this may create the opposite effect.
  • The order of login modules can be visually changed in Administrator Console from Edit Authentication Groups within Manage Applications.
  • Custom Single Sign on Login integration (Remote Auth) is possible, starting with this release. It involves a Remote Authentication CGI script where proxy will redirect the request to validate credentials if a new session is necessary and then the script returns back to proxy via HMAC.
  • Some more advanced elements were introduced for sources and for authentication configuration to cover complex rewritten and authentication scenarios.

The detailed list of changes is available in MuseKnowledge™ Proxy Release Notes PDF Document. As usual, we offer a Free 30 Day Trial period to fully evaluate the new version of MuseKnowledge Proxy. You can request a Trial License Key by simply filling in the trial form.

A new version of Muse™ Proxy was released on 21 June 2018. Muse™ Proxy version 5.0 is now available for download, trial and purchase/upgrade. The highlights of the new version are presented below.

Starting with this version, Muse™ Proxy supports relaying and filtering the WebSocket Protocol. According to the RFC 6455 the theoretic definition is: “The WebSocket Protocol enables two-way communication between a client running untrusted code in a controlled environment to a remote host that has opted-in to communications from that code”. To control WebSocket filtering and frame serialization mode the WEBSOCKET configuration element was introduced in the source profile.

A new proxy application template, MKPF, with a new look and feel is available. MuseProxyFoundation, the old one is still maintained and available with all the features up to date. On a fresh install Anonymous, MuseProxyFoundation and MKPF will all be installed and available, while on an update MKPF will be installed but not linked to in the Applications.xml file to avoid compatibility issues.

The Administrator Console is now based on a new theme and a new component is available to help the administrator of Muse™ Proxy to manage and maintain the applications and their sources.
This section can be accessed from the Applications menu via the Manage Applications link as long as SERVLET_ENGINE_ENABLED is set on true. There are visual actions for the common elements and raw view/update actions, where directly the XML files behind are edited in a simple JavaScript editor ensuring XML well-formedness. An application can be edited, copied, exported, imported, backed up, restored, checked or deleted. A source can have its profile edited, backed up and restored, while the other attributes from the Sources.xml file related to a source, such as image, visibility, module, attributes and parameters can be also managed. Source grouping including defining new visual areas and categories is also possible. Authentication to an application can be managed, details for the login module set and their configuration files can be edited in a raw XML form. The Manage Applications tools work with the last MKPF and old-style MuseProxyFoundation provided with the current setup, while for the existent applications not all the functions will be active.

A Muse™ Proxy source can be integrated with OLSA API to create the user dynamically and perform the signon. This is based on SOAP requests which are made transparently when the configured source with this integration is accessed by a Muse™ Proxy user. If all the configurations related to the organization are done, with this new feature a user of Muse™ Proxy application can jump into the Skillsoft Skillport 8i platform as an authenticated user of this platform without the need for continuous content proxy rewriting.

The integration within a Learning Management System (LMS) was extended and starting with this version, a Muse™ Proxy application can be integrated as Rich Content Editor in a Canvas LMS. Note that only the latest MuseProxyFoundation and MKPF applications can be integrated.

Starting with this version the ProxyLoginModuleLDAP can be configured with a script to take final decisions based on attributes and membership of user which log in. Also in this module, the referral configuration for LDAP authentication is possible via the new REFERRAL element with either ignore, follow or stop values. Two new attributes have been added, startTls="false/true" and sslTrustAll="false/true", ensuring a wider integration of Muse™ Proxy with LDAP servers. More details can be found in the comments from ProxyLoginModuleLDAP.xml and in the manuals.

In addition to the ECMA script processing via the Oracle Nashorn engine, the reference process in a source profile can now be done via BeanShell scripting engine.

A new CLASSPATH structure to create ClassLoaders was added in the MuseProxy.xml configuration file in order to reliably support third party libraries for various platform integrations in Muse™ Proxy.

A new pattern option, named excludeLocal, was added in order to exclude from main source(Link Out) but rewrite with others if matching. This option can be used within include and exclude pattern options from REWRITTING_PATTERNS configuration entry from the source profile.

A new element EXPIRY_ERROR inside the Applications.xml file was added in order to specify a response status for an expired application and if the specific error message will be displayed or not based on flag value of this configuration.

A new attribute method was added for URL configuration entry from the source profile to specify which HTTP method to be used for the request done – each URL part of an extract and navigate scenario can have its own method attribute (if empty GET or POST is assumed).

The HEADER element is a new configuration item in the source profile aiming to set HTTP headers for each preliminary request.

An option to refresh java policy files was added in Administrator Console and can be found under Advanced menu – Operations page. Java Policy Files which will be refreshed by this action are ${MUSE_HOME}/java.policy and ${MUSE_HOME}/jaas.policy.

In the Administrator Console was added support to refresh SAML and SSO configurations without restarting the entire Servlet Engine.

For source profiling a new boolean flag, DYN_HOST_MAPPING is available. It indicates that host mapping to a shorter generated value will be used on the fly if the https version of the host label exceeds 63 characters.

The detailed list of changes is available in Muse™ Proxy Release Notes PDF Document and the new features are described in the manuals that are part of the distribution. As usual, we offer a Free 30 Day Trial period to fully evaluate the new version of Muse™ Proxy. You can request a Trial License Key by simply filling in the trial form.

MuseKnowledge™ Application 6.0 is our latest web interface that replaces the older and well known MuseSearch™ Application series, used for more than a decade to search thousands of e-resources on the Internet.

Built on a whole new concept with a brand new look, the new interface keeps all the traditional features of MuseSearch™ plus a long list of new ones. The Muse® Core API was extended and lightened to deliver a faster and more responsive web interface which is now a Single Page Application that uses the latest web technologies like AngulaJS, Bootstrap and Font Awesome. This delivers a thoroughly updated and more responsive user experience.

The new MuseKnowledge™ Application is suitable to be used for any device, phone, tablet or PC. It is integration-ready, and playing it inside a parent site is now easier, be it a simple container or a more complex one like a Liferay Portal. It is embedded in both iOS and Android native code, allowing users ultimate flexibility to access more MuseKnowledge™ Applications from their mobile devices.

Last but not least, the Muse® Console for Application Administration has many improvements in sync with the new MuseKnowledge™ features and makes administering any older MuseSearch™ Applications much easier.

As usual we offer a Free 30 Day Trial period to fully evaluate the new version of MuseKnowledge™ Application. You can request a Trial License Key by simply filling in the trial form.

We are committed to providing good solid support for all Java versions our customers run The Muse™ Platform on. However, as new versions of Java, web browsers, and in general software technologies, are released, it is becoming more and more difficult to provide support for old Muse™ versions running on old Java versions which are out of support and lack new important features and security related standards.

More exactly, starting with July 1st 2017 we are no longer supporting the following Muse™ versions which run only with Java 6:

- Muse™ 2.5, released on 2010-10-07
- Muse™ 2.6, released on 2012-06-26

Java 6, end of its support life in February 2013. []

Java 9 is now expected to be released on 2017-07-27.[]

Technically, starting July 1st 2017, Muse™ Building Environment will no longer produce binary code compatible with Java 6. We will start compiling the entire Muse™ Platform including Muse™ Source Packages for Java Virtual Machine 8, hence they will no longer run under Java Virtual Machine 6.

Note that Muse™ versions 2.5 and 2.6 are not running with newer Java 8 versions.

Your 2.5 and 2.6 Muse™ installations will continue to function after July 1st 2017 according to your Licensing Agreement, however they will no longer be able to run automatic or manual updates that we provide via Muse™ Source Factory. If by July 1st 2017 you still run one of the old Muse™ versions – 2.5 or 2.6 – you must turn OFF the Muse™ Control Center task doing the automatic updates of the Muse™ Source Packages.

Please address your concerns with our Technical Support Department at or any questions you may have regarding this change.

We recommend that you start upgrading your customer installations to using Muse™ version 2.7 and the latest Oracle Java 8 build. Note that your existing Muse™ Applications user (web) interface should continue to run or require minimal compatibility fixes, under Muse™ version 2.7. If very particular cases arise we can create custom patches to accommodate this.

We make the same suggestion of contacting our Technical Support Department at for any questions and help regarding this upgrade.

The outstanding features from the new 4.3 version of MuseKnowledge™ Proxy are now ready to be used through the availability of this version for downloadtrial and purchase/upgrade.

To widen the authentication integration scenarios MuseKnowledge™ Proxy now supports a wide range of OAuth, OAuth2, OpenID Connect Single Sign on its entry point. Although the initial target was for Google authentication more than a dozen of OAuth providers and also a generic OAuth client implementation can be configured for authentication to the providers that are not diverging from the usual practices in OAuth requests and responses. The out of the box OAuth support is for: BitBucket, DropBox, Facebook, Foursquare, Github, Google, LinkedIn, ORCiD, Paypal, Strava, Twitter, Vk, Windows Live, Word Press, Yahoo. Note that Google authentication ensures authentication with both the public domain as well as Google hosted institutions via Google Apps for Education, for example.

To cover the cases in which we need to use an existent HTTP service or even a HTML login form existent in the intranet for authentication into a MuseKnowledge™ Proxy application the development team created the External HTTP Authentication Login Module. Upon authentication MuseKnowledge™ Proxy logon page is presented and the request to the remote HTTP login end-point is made as part of an extract and navigate scenario taking a success/fail decision based on elements from the page.

Changes in the source presentation layer allows for source categorization in multiple classes (areas). Multiple areas such as Subject, Vendor, Flat, Alphabetical (A-Z) can be defined and these are displayed in different tabs. Integration with MuseSearch passthrough is also possible if dblist mappings are defined. The MuseProxyFoundation application interface has improved its look and feel to accommodate the categorization.

Three new Administration Console pages SSO Authentication, HMAC Link Generator and Evaluate Regex are available in order to help on with OAuth SSO, HMAC testing and with simulating how RegEx filters works.

HAProxy PROXY Protocol v1 and X-Forwarded-For are supported by MuseKnowledge™ Proxy in order to get the end-user IP from load balancers that do not spoof/masquerade the end-user IP in the TPC/IP packets but have other logical means of sending the IP.

An alternative extract and navigation implementation based on the Apache HTTPClient is available and can be selected on a source by source basis. This is an alternative to using the JDK URLConnection library which does not offer lower level access to source IP and we were forced to perform an extra request.

Follow-up links without authentication (session cookie) such as for the preflight OPTIONS where the CORS standard requires the browser to avoid sending authorization data (hence no cookie session) are supported based on a new source configuration element.

The detailed list of changes is available in MuseKnowledge™ Proxy Release Notes PDF Document and the new features are described in the manuals that are part of the distribution. As usual we offer a Free 30 Day Trial period to fully evaluate the new version of MuseKnowledge Proxy. You can request a Trial License Key by simply filling in the trial form.