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!
Update your Profile with your Support type to get your Support Type badge.
Uncover the power of data with the Analytics Hub —your ultimate guide to mastering NetSuite Saved Searches and Reports. Simplify the complex and unlock your organization's true potential. Dive into the Analytics Hub now and soar to new heights!
Nominate Your Peers for NetSuite Support Community's Choice of the Quarter! Submit your nomination today.
Intelligent Payment Automation version 1.0.3 is now available in the SuiteApp Marketplace. The SuiteApp, powered by BILL, lets you automate payments, manage vendor details, and bank account information within NetSuite. Learn more
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. Explore new breakthroughs, sharpen your skills, and connect with experts who are shaping what’s next. Experience bold keynotes, interactive learning, and connections that span the global NetSuite community. Discover what's next at SuiteConnect Tour 2026.

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 4 (Oct-Dec 2025)

This Week's Leaders

This Month's Leaders

All Time Leaders