Paul,

I have tried the session state suggestion without success. The timeout still occurs around 20 minutes. I haven't setup the Forms section you mention below. If I were to do this, would I need to create one for each form in the application?

Also, please remember that I am using MM.NET and have just enabled security on forms by overriding the OnInit method as instructed in the MM.NET guide:

protected override void OnInit(EventArgs e)
    {
        this.RequiresSecurity = true;
        base.OnInit(e);
    }

Thanks again in advance for your help.

Bob

>>Paul,
>>
>>Thanks for your reply. I checked the blog but it confused me a bit, so I will ask you since you are an experienced MM.NET user. What I am trying to accomplish is increasing the amount of time a user would get in an MM.NET secured application before MM.NET asks for login information again.
>>
>>What settings would I need to modify to adjust this?
>>
>
>Sorry, must have missed this message. I don't have it installed here to test it, but I would assume you could edit both the session expiration and form expiration times in the web.config (assuming you're actually using form based authentication) ex.
>
>

><system.web>
>   <sessionState mode="InProc" cookieless="false" timeout="60" />
>

>
>and
>
>

><authentication mode="Forms">
>      <forms name="MyForm" timeout="60" loginUrl="/Login.aspx" protection="All" slidingExpiration="true" path="/" />
>    </authentication>
>