FAQ Tag: session

How to increase the inactivity timeout of a Muse Proxy Application?

The default session timeout of a Muse Proxy Application is of 30 minutes. When the authentication session of the Muse Proxy Application is close to end, a Session Timeout warning pop-up and/or a Session Timeout warning window will appear. Each of them displays a message which notifies the user regarding the remaining time from the…

When a Muse session expires (times out)or after my user clicks “logoff” they should be redirected to my web site (or another a

The following must be done to achieve this functionality: 1. Search the $APPLICATION_HOME/www folder for files containing an HTML form called “logoffForm”. 2. In the files found at #1 add the following in the “logoffForm”: , where app_name is the name of the Application you’re working with. 3. In the $MUSE_HOME/web/www/logon folder create a folder…

How can I set the maximum number of simultaneous sessions?

1) At the application level: This can be done by changing the value of the “User Concurrent Sessions” field from the application’s properties using the Muse Admin Console. The file from within the application which contains this setting is $APPLICATION_HOME/profile.xml, field: <MAX_USER_CONCURRENT_SESSIONS>. Note that this field sets the maximum number of simultaneous sessions for one…

Does a new Muse session start every time we connect through our Bridge?

A new Muse session starts every time you perform a LOGON action through the Bridge. The session is then active until you perform a LOGOFF action or until it times out. You may do multiple SEARCH actions through the Bridge in one LOGON session.

How can I set the maximum number of simultaneous sessions?

1) At the application level: This can be done by changing the value of the “User Concurrent Sessions” field from the application’s properties using the Muse Admin Console. The file from within the application which contains this setting is $APPLICATION_HOME/profile.xml, field: <MAX_USER_CONCURRENT_SESSIONS>. Note that this field sets the maximum number of simultaneous sessions for one…

When I test/search many Sources at a time some fail, but when searched individually they work.

If all Sources work within a Muse application individually but some fail when they are searched together, this is an indication that the target site(s) and/or your Internet connection might be slow or under stress conditions. First check the following: – Is the Internet connection slow? Check independently (outside of Muse) to see if the…

Where are the Navigation Sessions used?

The Navigation Sessions are used only by the ‘Navigation Manager’ Web Context (the Muse Navigation Manager component) to store useful data regarding a specific link navigation using a certain target site authentication context (cookies, referrer, next proxy access details, encoding etc.) through Muse Navigation Manager. This type of session is managed using an ID (named…

Where are the Client Sessions used?

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…