Home > Articles

  • Print
  • + Share This
This chapter is from the book

Session Tracking

In order to associate the user's session with a particular browser, WAS needs to maintain some form of association with the client browser. There are several techniques available, and we'll detail them here. It is important to note that while WAS allows for great flexibility in choosing the tracking mechanism, cookies are by far the best approach.

Cookies

The use of a cookie for tracking session state is the default in WAS. This option differs from a pure cookie-based solution in that the HTTP session uses a single cookie named JSESSIONID that contains the session ID, which is used to associate the request with information stored on the server for that session ID, while an entirely cookie-based solution would employ multiple cookies, each containing possibly sensitive user state information (account number, user ID, etc.). With HTTP session, all attributes associated with the user's request are stored on the server. Since the only information transmitted between the server and the browser is the session ID cookie, which has a limited lifetime, HTTP session can provide a much more secure mechanism than cookies for tracking application state when configured in conjunction with SSL.

The mechanics of using a cookie for tracking session are depicted in Figure 22-1. A request arrives at the server requiring that a session be created as the result of a getSession() method call. The server creates a session object, associating a session ID with it. The session ID is transmitted back to the browser as part of the response header and stored with the rest of the cookies in the browser. On subsequent requests from the browser, the session ID is transmitted as part of the request header, allowing the application to associate each request for a given session ID with prior requests from that user.

The interaction between browser, application server, and application are all handled transparently to the end user and the application program, aside from the getSession() method call inside the application. The application and the user need not be, nor are they likely aware of the session ID provided by the server.

Figure 22.1Figure 22-1 Browser-session manager cookie interaction.

Unfortunately, not all users configure their browsers to accept cookies. Often, this is related to security concerns over accepting a cookie into the browser. Most often the restrictions on accepting a cookie into the browser are the result of concerns about persistent cookies. Persistent cookies remain in the browser after the browser is closed and allow a web site to "remember" you on ensuing visits. Most important in terms of presenting a risk, persistent cookies may contain personal information about you, which is then accessible to any application that has access to the cookie folder in your browser. However, WAS generates a session cookie that exists only until the browser has been closed and is used only to ensure that you are "recognized" as you move from page to page within the web site. This technique is not generally considered to be a security or privacy concern. In fact, most modern browsers can be configured to accept all session cookies while still blocking persistent cookies.

Finally, in a WAS environment with security enabled, disabling all cookies is actually counterproductive since the most often used authentication mechanism is LTPA (Lightweight Third Party Authentication), and LTPA relies on creating a token (cookie) that is used to represent the identity of the authenticated user to the browser. In any event, other options exist for maintaining an application state such as URL rewriting, although they are not recommended.

URL Rewriting

Most often, URL rewriting is employed when a browser is configured not to accept cookies. URL rewriting stores the session identifier in the page returned to the user. WAS encodes the session identifier as a parameter on any link or form the user submits from a web page. This option requires that the Servlet code be modified to include either an encodeURL() or encodeRedirectURL() method. When a browser user clicks on a link that utilizes one of these methods, the session identifier passes into the request as a parameter, with the result shown in Figure 22-2, where the session ID is appended to the URL for the web page.

Figure 22.2Figure 22-2 URL rewriting example in browser.

The requirement that the application developer write additional code for a Servlet or JSP presents a major disadvantage for URL rewriting when compared to other available session tracking mechanisms. Additionally, URL rewriting limits the flow of site pages exclusively to dynamically generated pages (those generated by Servlets or JSPs). While WAS can insert the session ID into dynamic pages, it cannot insert the user's session ID into static pages (.htm or .html pages). As a result, after the application creates the user's session data, the user must visit dynamically generated pages exclusively until he or she finishes with the portion of the site requiring sessions. URL rewriting forces the site designer to plan the user's flow in the site to avoid losing his or her session ID. Lastly, the system administrator must configure WAS to enable URL rewriting by checking the box shown in Figure 22-3.

Figure 22.3Figure 22-3 Session tracking mechanism dialog.

Fortunately, the WAS session management implementation can recognize when a browser is configured to accept cookies and will use this option instead of URL rewriting in cases when both cookies and URL rewriting are enabled.

SSL ID Tracking

Another alternative tracking mechanism is the Secure Socket Layer (SSL) ID that is negotiated between the web browser and the HTTP server. While secure, this alternative presents a number of disadvantages. Since this ID is negotiated between the browser and the HTTP server, the failure of the HTTP server results in the loss of this ID. In a clustered environment, the IP sprayer used to direct requests to the HTTP servers must provide some sort of affinity mechanism so that browser requests return to the HTTP server that negotiated the ID with the browser. Additionally, in a clustered environment with multiple application servers, either cookies or URL rewriting must be enabled for affinity between the HTTP server and application server. Lastly, in a fashion similar to URL rewriting, the administrator must also explicitly configure WAS to employ this option by selecting this option on the configuration dialog (refer to Figure 22-3).

  • + Share This
  • 🔖 Save To Your Account

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.

Overview


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information


To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.

Surveys

Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.

Newsletters

If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information


Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.

Security


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.

Children


This site is not directed to children under the age of 13.

Marketing


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information


If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.

Choice/Opt-out


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information


Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents


California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure


Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.

Links


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact


Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice


We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020