ASP and SQL

It's with regards to the ASP, and session vairables.
I am doing a Web site where it's security enforced.It's similiar in the project you assigned us.  A user logs in and from that login we determine was information they are allowed to see and what they can access.  So reference to the login variable is gonna be needed all throughout
the pages.  So session variables are the way to go right?  But session variables don't last long...(default is 20) I am gonna need it for more than that and well all I have to do is set the timeout for the session to be a larger number.  That will do it won't it?  Pretty sure it will
providing the timeout period is longer right?  I would be able to talk to different pages within a frameset and the session variable would still be alive right?  Is this my best approach or is there a better option.
Thanks for any HELP.

lobosAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

sybeCommented:
The sessionvariables "die" x minutes after the last user's activity. So they won't die when a user is visiting your website and asking for pages for about 2 hours.
Sessionvariables are bound to cookies, so the browser has to accept cookies. I am not sure how "hack-resistant" cookies are, so if your information is very sensitive, you might want to use another solution then session-variables (for example NT-security, you can ask for login-name with ASP).

About this "hacking": I have never really tried to do it. But I noticed that ASP-cookies have a code that is given out in a certain order to new visitors. So if visitor A gets cookie "ASP-4565421" visitor be would get "ASP-4565422". Someone could try to change the value of the cookie in his browser and get the security of another user.

Maybe it is possible to make the ASP-cookies be more random, I haven't looked for it. I solve possible security stuff through NT-security and use cookies (and sessionvariables) only for non-sensitive things.
0
ny_skyCommented:
If Transaction Server is a possibility then you can utilize the role assignments for a given package.  You can add NT groups to each package and validate whether or not a user is in a particular group through the Object Context.  The method "IsCallerInRole" will check to see if that user is in the role (or group) you have created.  Based on the value returned you can use a simple if statement in the asp page and populate the values applicable to their security level.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server

From novice to tech pro — start learning today.