Sorry, I meant CONNECTORS-737. Basically we need an associated session in order to keep track of data that we aren't including in the HTML. That implies a session that expires, and when it does, there is a need to log in again.
Karl On Wed, Aug 14, 2013 at 10:48 AM, Karl Wright <[email protected]> wrote: > I have no issue with raising the default session timeout to 30 minutes. > As for disabling the security, please see CONNECTORS-730 for a > description of the reasons why that would be difficult. > > Karl > > Sent from my Windows Phone > From: Erlend Garåsen > Sent: 8/14/2013 10:32 AM > To: [email protected] > Subject: Change the crawler UI authentication model? > > I think it is advisable to change how the crawler UI authentication > works, at least make it possible to deactivate it. > > - The session timeout value is too short. Web applications usually have > a timeout value set to 30 minutes. > - The context is not remembered. If you are entering/editing a complex > exclude list for a job and pressing "Save" after, say, 10 minutes, > everything is lost. Many authentication models remember the last action > and perform that action after reauthentication. > > The latter is probably more complex to fix, but a longer session > duration will probably solve the problem of lost work. > > What do you others think? > > Erlend >
