FAQ

Such and error may occur in 2 cases: A. the username and password used to access the Global InfoBase are not correct and/or B. the Muse communication with Global InfoBase is not successful. A. The u/p used to access the Global InfoBase are set for each admin user via Designer console or Muse Console for Applications Administration. Using Muse Console for Applications Administration (starting with Muse 2300), the Global InfoBase u/p can be changed as following: – log in Muse Console for Applications Administration, – go to “Users”, – select a user and click “Edit Properties”, – in the window that opens, set the “Global InfoBase User Name” and “Global InfoBase User Password”. Using Designer Admin console (before Muse 2300), the Global InfoBase u/p can be changed as following: – log in Designer console, – go to “Users”, – click “Muse Admin Bridge” , – click “Properties” of the admin user that must be checked, – in the window that opens, set the “Global InfoBase User Name” and “Global InfoBase User Password”. B. Unsuccessful communication between Muse and Global InfoBase can be caused by a transparent HTTP proxy between the two. The communication with Global InfoBase is based on XML requests and responses over TCP sockets. Many HTTP proxies cannot handle such XML requests and responses because the communication is not over the HTTP protocol and thus a HTTP proxy cannot handle it, because it tries to understand HTTP headers. Because of that, the message presented to the user is (Global InfoBase error: … Wrong user name or password.) since Muse does not get back a message confirming the successful authentication to Global InfoBase. The best solution for this case is to give full Internet access to the Muse server or at least to factory.museglobal.com:80. If this is not possible due to special security policies, we recommend the following workarounds:

• if the outgoing communication to port 8005 is not passed through the transparent proxy (and if there is no firewall blocking such requests on client side), change the port in the $MUSE_HOME/factory/SourceFactory.xml from 80 to 8005 (e.g. enter 8005 as value in the "" field).
• switch the communication of the Muse server with SourceFactory on SSL. Even if the traffic passes through proxy, being on SSL, the proxy will not interfere and the communication will stand. To do this, change the port in the $MUSE_HOME/factory/SourceFactory.xml from 80 to 443 (e.g. enter 443 as value in the "" field) and also set field to "yes". Please note that this option is only available fro Muse versions 2.3.1.1 and above.

Note: After such a port change, Muse HTTP server/Apache Tomcat must be restarted.

There is a “Forgot your password? Recover it.” feature in the Muse applications. When clicking on it, an email containing the configured password will be sent at the user’s email address. For this feature to work, the email settings configured at the application level must be correct and working.
Also, this feature is accessible from within the application, in other words you must login into the application in order to access the “Forgot your password? Recover it.” feature.
In the case of an application configured with IP authentication for “in Campus” and Personal User for “off Campus” access, the end user can access the “Forgot your password? Recover it.” feature only from in Campus.

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.
– ProxyLoginModuleIMAP. Performs authentication against a IMAP Server. The IMAP authentication module supports NONE, SSL or TLS connection encryptions.
–ProxyLoginModuleSQL. Performs authentication against an SQL Server through Java Database Connectivity (JDBC). The SQL authentication module supports NONE, SSL or TLS connection encryptions.
–ProxyLoginModuleReferer.Performs authentication against the client’s referer URL.

You can read more about the authentication in a Muse Proxy Application in the “Muse Proxy.pdf” manual, chapter “Authentication of a Muse Proxy Application”.