FAQ Tag: authentication

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…

Elsevier does not permit HTTP access to their resources through federated search products. For federated search Elsevier provides specialized APIs for which we have the following Source Packages: ScienceDirectRESTXML, ScienceDirectRESTXMLBooks, ScienceDirectRESTXMLJournals and ScopusRESTXML. Arrangements with Elsevier for this access must be handled by you (the partner), or by your customer, following the steps below: Install…

The Client Sessions are used by the Muse Proxy Web Contexts which perform authentication in order to store the client authentication status to that Web Context, as well as other user metadata. When a request comes to Muse Proxy (as a web server) without a Client Session cookie, a Client Session ID will be generated…

Muse Proxy Authentication Token authenticates a rewritten request with an authentication token generated by Muse Proxy. The authentication tokens are generated in the following cases: A) when a rewritten link is generated using the ‘Utilities >> Rewrite URL’ section from the Muse Proxy Administrator Console and the ‘Muse Proxy Authentication Token’ option is selected. The…

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…

You can configure LDAP authentication as a single authentication method. The steps are: – copy the ${MUSE_HOME}/use/ice/profiles/ICELoginModuleLDAP.xml file into the application which is to be configured, into the ${MUSE_HOME}/home/ApplicationID/profiles/ folder, where replace ApplicationID with the exact application ID you wish to configure with LDAP authentication. – configure the necessary Muse login modules for the application….

The overall steps would be: 1) Create the new application as copy of the MuseProxyFoundation template, the ID of the new application to be MuseProxyFoundationHMAC for example. 2) Edit the file $MUSE_HOME\proxy\webcontexts\Applications\MuseProxyFoundationHMAC\ profiles\AuthenticationGroups.xml and do the following: – Locate the /ICE-CONFIG/AUTHENTICATION_GROUPS/AUTHENTICATION_GROUP/AUTHENTICATIONS node and remove its content, thus obtaining an empty node: <AUTHENTICATIONS> </AUTHENTICATIONS> – Edit…

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. –…

The PERSISTENT-URL (sometimes also called durable URLs or durable links) is a url to a detailed native record and it is specifically not rewritten by Muse Navigation Manager. The PERSISTENT-URL link was created as an URL for which the users will use their own authentication to access the native data. The PERSISTENT-URL was specifically designed…