[jcifs] NtlmSsp - Closing sessions?

[Michael B. Allen]

Incedentally the NtlmHttpFilter sets jcifs.smb.client.soTimeout to 5 min:

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

On Tue, 17 Dec 2002 18:53:40 -0500
"Allen, Michael B (RSCH)" <Michael_B_Allen at ml.com> wrote:

> All operations performed under the same credentials are multiplexed over the same
> session. So for any domain/username/password combination there is one
> SmbSession. If there is no activity on the SmbTransport associated with the
> SmbSession for jcifs.smb.client.soTomeout milliseconds or longer, all SmbSessions
> will be logged off and the SmbTransport will be closed. Currently I do not feel these
> details should be exposed to the user. Only in certain pathological cases would the
> number of unused SmbSessions become prohibitively expensive. It is not perfectly
> clear to me that your requirements fall into this category but for now we are requiring
> users to make the necessary changes to the code themselves. For example, one easy
> modification that could be made is to simply add something like:
> 
>     public static SmbSession getSmbSession( UniAddress server, NtlmPasswordAuthentication auth ) throws SmbException {
>         return SmbTransport.getSmbTransport( server, 0 ).getSmbSession( auth );
>     }
> 
> to SmbSession and publicize logoff(). But I would profile the default deallocation behavior
> and determine with certainty that such a modification is really necessary.
> 
> > -----Original Message-----
> > From:	Bazyl, Steven [SMTP:sbazyl at rsasecurity.com]
> > Sent:	Tuesday, December 17, 2002 5:44 PM
> > To:	'jcifs at lists.samba.org'
> > Subject:	[jcifs] NtlmSsp - Closing sessions?
> > 
> > I'm interested in using the NtlmSSP interface but while looking through the
> > source I noticed that it is not possible to terminate individual sessions
> > (nor even get an SmbSession reference - its not part of public API.)  This
> > may be a problem if handling lots of authentications, particular when the
> > primary interest is in initial authentication (such as with the servlet
> > filter) rather than a prolonged/interactive sessions.  I just want to do
> > something like the following:
> > 
> > ...
> > SmbSession session = null;
> > try {
> >   session = SmbSession.logon( dc, authinfo );
> > } catch( SmbAuthException e ) {
> >   // handle invalid login...
> > } catch( SmbException e ) {
> >   // handle general failure...
> > } finally {
> >   if( session != null ) {
> >     session.logoff();
> > }
> > 
> > 
> > Any thoughts on making the following changes?
> > 
> > - Change SmbSession.logon to return the SmbSession instance.
> > - Make SmbSession.logoff(...) public.  Also have it remove the session from
> > the SmbTransport's list of sessions.
> > 
> > -Steve
> > 
> > 
> >     
> 


-- 
A  program should be written to model the concepts of the task it
performs rather than the physical world or a process because this
maximizes  the  potential  for it to be applied to tasks that are
conceptually  similar and, more important, to tasks that have not
yet been conceived.