Muse® Proxy
The last four months of development work for MuseKnowledge™ Proxy has summed up in the new 4.5 release available for download, trial and purchase/upgrade since October 5th, 2017. The outcome of listening to our partners and innovating work can be shortly described as below.
Learning Tools Interoperability® (LTI®) integration with MuseKnowledge Proxy is available – a MuseKnowledge Proxy application or a proxified source can be used as an External Tool within a Learning Management System (LMS) using the LTI® launch requests standard. For helping with LTI configuration, a new button
named “LTI Guidlines” was added into the MuseKnowledge™ Proxy Administrator Console, Configuration – SSO Authentication page. It contains detailed guidelines to configure LTI for a MuseKnowledge™ Proxy Application.
HTTP headers from requests and responses can be processed using one or more HEADER
elements within a new or existent FILTER
. Optionally, dynamic processing via scripting is possible.
A better experience can be achieved for serving static resources within MuseKnowledge Proxy application interfaces by using the new authenticationFlow
FILE_SET
TYPE
.
Special variables (such as the user ID that is also logged, the application URL) can be referred by using the new element PARAMETER/REF
. These can further be used in JavaScript functions defined in the DEF
section for dynamically obtaining a token or a full URL from a service via an API, which will then be used as a starting point for the current navigation, either dropping the proxy or by further rewriting.
Support for dynamic ClassPath for bridging external Java code from the DEF
source section without having to add library jar files to the system ClassLoader, as well as, support for Nashorn scripting mode allowing to call external processes through Unix shell like back quote strings was added, for now experimentally, to further explore more integration possibilities.
Type1 Links generated by MuseKnowledge search connectors can now point to a MuseKnowledge Proxy application root to cover cases where a higher level of rewriting configuration is necessary.
A new option, SERVER_TOKENS
, is available for configuring the Server header field for the content served directly by MuseKnowledge™ Proxy.
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.
A new version of MuseKnowledge™ Proxy, 4.4, is now ready and available for download, trial and purchase/upgrade. Some of the new features, improvements and bug fixes are mentioned below.
Multi-tenant environments using the same DNS host name for all tenants, but individual IPs for each one are now more efficiently handled as a chaining request to proxy itself on the different IP is minimized for the first source request only. The follow-up rewritten requests are not chained. The outbound IP is set directly to the one assigned for the tenant. This scenario is minimizing the cost for SSL certificates which are now more often required.
Starting with version 4.4 Muse Proxy creates access log files in the same configurable format as that used by standard web servers such as Apache HTTP Server, format which can be set via a %
style pattern – an extension to the Common Logging format.
Central Authentication Service (CAS) and Microsoft Azure AD OpenID Connect authentication are now added to the possible Single Sign-on integration scenarios. The Administrator Console is offering guidelines for treating the special case of Azure AD where a different callback type is needed.
The direct authentication SQL module now supports SQL statements to cover more complex scenarios – the old approach of using a single table is still working.
In case of HMAC and IP login modules there’s no end user ID to check against a database and hence nothing to be written in the log file, however, in case of various integrations a special parameter could be received in the request for tracking purposes and it is now possible to configure it.
This new version is introducing redirection to remote Sources depending on the end-user IP (non-proxied links) and on the source ID.
Informal ranges of IPs for authentication to a MuseKnowledge™ Proxy application and for source redirection rules are now supported. All types of rules can be mixed for ALLOW/DENY
: CIDR, patterns, exact IP and ranges.
After a mnm.jar
update, the existing navigation sessions continue to work with the FIND/REPLACE
filters.
The necessary upgrades steps to be done are listed at the end of the MuseKnowledge™ Proxy Setup in case an upgrade is performed over an existing isntallation.
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.