megaphone
Update your Profile with your Support type to get your Support Type badge.
Nominate Your Peers for NetSuite Support Community's Choice of the Quarter! Submit your nomination today.
Expand your NetSuite knowledge by joining our Ask A Guru Live sessions. RSVP on this event now.
Stay in the know of how NetSuite can help grow your business with our guides, webinars, and events. Subscribe Here
What Topic Should We Cover Next? Your idea could be our next feature—drop your suggestion now!
No Limits. Just possibilities. Join us for complimentary one-day events around the world and step into a future fueled by AI and limitless potential. Discover what's next at SuiteConnect Tour 2026.
Try Intelligent Payment Automation – Fee Free For Your First Month For more information, visit this thread.
Don't miss out on our Pop Quiz! You only have until tomorrow, March 17, 2026, 2:00PM ET to comment your answers.

Discussions
Stay up-to-date with the latest news from NetSuite. You’ll be in the know about how to connect with peers and take your business to new heights at our virtual, in-person, on demand events, and much more.
Now is the time to ask your NetSuite-savvy friends and colleagues to join the NetSuite Support Community! Refer now! Click here to watch and learn more!
Stay in the Know

Be sure you're subscribed to NetSuite communication to stay in the know about monthly happenings, updates and announcements. Subscribe

Session and Login Issues with Password Protected web store

edited Dec 3, 2019 2:52PM in General 3 comments

Here are a few issues I have found with session management in the webstore:

1. Login to a secure password protected web store and nlobjContext will contain the user's customer record ID. Logout and the context still contains the user's customer record ID. Clear cache and history, Close the browser, reboot your machine, relaunch browser and context still contains the user's customer record ID. This is not good if user's share same computer but login under different customer records.

-update: 2013-Mar-29: This is still true.

2. Login and use nlobjContext.setSessionObject to save a session variable. Logout and view nlobjContext.getSessionObject and the variable is empty (that's good). Log back in and view nlobjContext.getSessionObject and the variable contains the value from the previous session (that's bad).

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!

Leaderboard

Community Whiz

Quarter 1 (Jan-Mar 2026)

This Week's Leaders

This Month's Leaders

All Time Leaders