FAQ Tag: ip

To configure an application that uses username/password authentication method to use also IP authentication, one must do some configurations. A) For Muse version 2500, the admin console can be used to add/edit the IP authentication of a Muse application: – log into the MCAA console as a mcaa based user; – select the desired Muse…

The functioning principle of this authentication scenario is as follows: – the enduser accesses the provided Muse URL; – if the enduser’s IP is among the IPs/subnets configured for the desired application then he/she will be successfully logged in; – if the enduser is not IP authenticated then he/she will be presented with a Muse…

This is explained in the “Adding a new slave machine to the environment” chapter from the “Muse Advanced Configuration.pdf” manual. In a shared Muse environment all files are shared, including the $ICE_HOME/serial.properties file containing licensing information and necessary for the ICE to start. When adding new servers to a Muse cluster one cannot just run…

The hosts.xml files are used to allow/deny access to different products from some IPs or classes of IPs. The client’s IP is tested against the rules in the hosts.xml file and the first one that matches is applied – all the following rules are ignored. When getting the hostname related to a given IP the…

When one or more new IPs are added to a machine running Muse ICE, ICE will not start again until the Muse product is re-registered. Running the Muse Registration process ensures that all the current IPs of the machine are added to the serial.properties file, which is required for the Muse ICE server to start…

One can specify an IP address for Muse Proxy to listen on for connections. By default, Muse Proxy listens on all IP addresses, on all interfaces. This setting can be changed in the ${MUSE_HOME}/proxy/MuseProxy.xml file by specifying an IP address in the “<BINDADDRESS>” field.

In Muse, there are 2 types of proxy chaining: a) “ProxyChaining” happens when the MNM chains with the proxy used for source authentication. In a Muse application where we have configured a MNM_HOST to re-write the record links and a PROXY_HOST to use for authentication we have the following scenarios: 1) If the MNM and…

MuseGlobal provides the following method for search and retrieval of EBSCOhost content: EBSCO Integration Toolkit (EIT) This is a SOAP-based Web Service approach which provides the optimal combination of performance and completeness. You can find the EIT Source Packages by searching in your Muse Console’s “Add Sources” section in the “IDs Containing” field for the…

For authenticating the end-users into a Muse Proxy Application the following authentication modules are available: –ProxyLoginModuleUserPassword. Performs User Name/Password authentication. –ProxyLoginModuleIP. Performs IP authentication based on client machine IP. –ProxyLoginModuleLDAP. Performs authentication against a LDAP Server. –ProxyLoginModuleFTP. Performs authentication against a FTP Server. The FTP authentication module supports NONE, SSL or TLS connection encryptions. –…