[jcifs] Re: question about ntlm http authentication

[Thomas Bley]

Hi Mike,

of course I've looked at the networkexplorer but unfortunately there is 
no documentation telling me exactly where my problem is solved:

It looks like the turning point is soTimeout, is it ?

 From the documentation:
jcifs.smb.client.soTimeout
To prevent the client from holding server resources unnecessarily, 
sockets are closed after this time period if there is no activity. This 
time is specified in milliseconds. The default is 15000.

=> For me it is not clear that this setting has an effect on the ntlm 
http authentication.

Config.setProperty( "jcifs.smb.client.soTimeout", "600000" );
Config.setProperty( "jcifs.smb.client.attrExpirationPeriod", "300000" );

using this doesn't work in init(). When I use System.setProperty the 
values are used.
With soTimeout=600000 I am no longer able to do a connect after an 
inactivity greater than 60 seconds (timeout exceptions). When I restart 
Tomcat it works again.
Using soTimeout 60000 seems to work.

bye
Tom


Michael B Allen wrote:
> On Sun, 18 Sep 2005 20:28:17 +0200
> Thomas Bley <thomas.bley at simple-groupware.de> wrote:
> 
> 
>>Hi Mike,
>>
>>using ntlm the authentication is valid for some seconds. When the user 
>>is inactive for 20-30 seconds, and clicks again in the webdisk, he gets 
>>a "access denied". So his browser has to provide the authentication 
>>again and the user gets the access again.
>>
>>Do you know if this behaviour can be configured in any way ?
>>(e.g. allowing 2 minutes of inactivity before giving access denied)
> 
> 
> I don't mean to be sarcastic but is there a reason why you're ignoring
> my advise to follow the NetworkExplorer.java code?
> 
> Mike
>