Home > Articles > Programming > Java

Securing Servlets and JSPs in Sun Java System Application Server, Part 2

Leonard Anghel concludes his series on security and the Sun Java System Application Server with a discussion of various security mechanisms, examples of the types of attacks you can expect, and suggestions on how to protect your websites against these malicious behaviors.
Like this article? We recommend

Part 1 of this series showed you how to use declarative security in the Sun Java System Application Server (SJSAS) deployment descriptors to declare roles, users, groups, and realms. In this article, we'll consider how to implement some of the main website security approaches. We'll start with the authentication mechanisms and then discuss security annotations, programmatic security, and common attacks on JSP pages.

Types of Authentication

Now that we've provided a database for users/groups and passwords, it's time to see how to authenticate a user for our web application. We'll consider four types of authentication:

  • HTTP basic authentication
  • Digest authentication
  • Form-based authentication
  • HTTPS authentication

We'll look at each type of authentication based on the realms we defined earlier.

HTTP Basic Authentication

HTTP basic authentication is based on probably the most common and intuitive authentication scenario. When trying to connect to the server, the user has to provide a username and a password through a built-in interface. The server compares the client's credentials against a database of authorized users and accepts or rejects the user based on this comparison. Translating the authentication handshake into steps, we have the following:

  1. A client tries to access a protected resource.
  2. The server displays a built-in interface that requires the user credentials (username and password).
  3. The client types the credentials and submits them to the server. (The password is sent in Base64 encoding.)
  4. The server compares these credentials against a realm. If the authentication succeeds, the user is given access to the protected resource.

You can activate this kind of authentication from the web.xml descriptor as follows:

<login-config>
 <auth-method>BASIC</auth-method>
  <realm-name>MyFileRealm</realm-name>
</login-config>

Use those lines to replace the following comment in your web.xml file:

<!-- here we will paste the authentication mechanism -->

In this case, we've used the MyFileRealm realm developed in part 1 of this series. This realm contains two users:

  • TimmyTom can access the JSP files from the /jsps folder (JSP-ROLE role, JSP-USERS group).
  • MaryJane can access the SecureServlet servlet (SERVLET-ROLE role, SERVLET-USERS group).

No other user can access these resources.

Digest Authentication

Digest authentication is much like HTTP basic authentication. The difference between the two mechanisms occurs at transport level. With digest authentication, the password is encrypted before it's transmitted through wires; with basic authentication, the password is easily cracked because it's just encoded with a Base64 algorithm.

SJSAS doesn't implement digest authentication. In principle, the lines that should be added to web.xml for servers that support digest authentication (such as Tomcat) are as follows:

<login-config>
 <auth-method>DIGEST</auth-method>
  <realm-name>{the_realm}</realm-name>
</login-config>

Form-Based Authentication

Probably the most frequently used authentication mechanism is form-based authentication. This kind of authentication improves on basic authentication by adding the capability of controlling the look and feel of the login interface. In addition, a rejected user is redirected to a custom error page, rather than simply receiving a "forbidden" error message. The steps of form-based authentication are as follows:

  1. A client tries to access a protected resource.
  2. The server redirects the user request to a custom interface that requires the user credentials (username and password). We named this interface login.jsp (see Figure 1).
  3. The client types the credentials and submits them to the server (via unsecured transport).
  4. The server compares these credentials against a realm. If the authentication succeeds, the user is given access to the protected resource. If authentication fails, the client is forwarded or redirected to a custom error page. We named the error page loginError.jsp.

You can activate this kind of authentication from the web.xml descriptor as follows:

<login-config>
 <auth-method>FORM</auth-method>
 <realm-name>MyJDBCRealm</realm-name>
 <form-login-config>
  <form-login-page>/jaas_login/login.jsp</form-login-page>
  <form-error-page>/jaas_login/loginError.jsp</form-error-page>
 </form-login-config>
</login-config>

Use those lines to replace the following comment in your web.xml file:

<!-- here we will paste the authentication mechanism -->

The login.jsp page code may look as follows:

<!-- j_security_check - the login form's action -->
<form method="POST" action="j_security_check">
 <table align="center" width="100">
  <tr bgcolor="#000000">
    <td>
     <font size="1" face="Arial" color="#ffffff">
      <strong>User:</strong>
     </font>
    </td>
    <td>
     <!-- j_username - the name of the username field -->
     <input type="text" name="j_username" />
    </td>
  </tr>
  <tr bgcolor="#000000">
    <td>
     <font size="1" face="Arial" color="#ffffff">
      <strong>Password:</strong>
     </font>
    </td>
    <td>
     <!-- j_password - the name of the password field -->
     <input type="password" name="j_password" />
    </td>
   </tr>
   <tr bgcolor="#000000">
    <td>
     <input type="submit" value="Login" />
    </td>
   </tr>
  </table>
 </form>
...

loginError.jsp doesn't contain any mandatory parts; therefore, you're free to use your imagination and develop the error page as you like.

In this case, we've used the MyJDBCRealm realm developed in part 1 of this series. This realm contains two users:

  • ShawnRay can access the JSP files from the /jsps folder (JSP-ROLE role, JSP-USERS group).
  • MarchusRuhl can access the SecureServlet servlet (SERVLET-ROLE role, SERVLET-USERS group).

No other user can access these resources.

HTTPS Authentication

HTTPS authentication is based on the SSL transport mechanism. This transport guarantees an encrypted communication between server and client, meant to ensure privacy for the transmitted data. Before any private data is transmitted, however, the server presents to the web browser a set of credentials in the form of a server certificate. (This procedure, known as the SSL handshake, must be completed before the HTTP request is accessed.)

In addition, the server may require that the client present in exchange a client certificate (in this case, we're talking about mutual authentication over SSL). The server certificate proves to the client that the site is who it claims to be, and the client certificate proves to the server that the client or user is who it claims to be.

In SJSAS, SSL support is enabled and ready to be used (by default, the SSL-HTTPS connector is activated and can be tested on https://localhost:8181/). For other servers, check the server documentation to see how to activate the SSL-HTTPS connector (if it isn't already activated).

Before specifying a secure connection, you should know that SSL is commonly used when the login authentication method is set to BASIC or FORM. Since these two authentication mechanisms are based on unsecured transport, it's a good idea to enforce them with the SSL transport support. The transport type is indicated in the web.xml descriptor through the <transport-guarantee> element. The values supported by this element are shown in the following table.

Value Description
NONE Unsecured transport.
INTEGRAL The data cannot be changed in transit between client and server.
CONFIDENTIAL The changed content is invisible to anyone/anything from outside the process.

Next, we set the CONFIDENTIAL security level for the SecureServlet resource:

<security-constraint>
 <web-resource-collection>
   <web-resource-name>Secure Servlet</web-resource-name>
   <url-pattern>/SecureServlet</url-pattern>
   <http-method>GET</http-method>
   <http-method>POST</http-method>
 </web-resource-collection>
   <auth-constraint>
     <role-name>SERVLET-ROLE</role-name>
   </auth-constraint>
   <user-data-constraint>
     <transport-guarantee>CONFIDENTIAL</transport-guarantee>
   </user-data-constraint>
</security-constraint>

Notice that the server proves its identity by showing the client the server's auto-signed certificate from mykeystore.jks. (We created this certificate in part 1, customizing the SJSAS configuration to point to our keystore and truststore instead of the defaults.) Depending on the browser, an attention message may be triggered, indicating that the certificate is self-signed and asking the user to accept it as a trust certificate. Once the certificate has been accepted, the user will not be prompted to accept the certificate again at the next connection.

Mutual Authentication Over SSL

When the server is proving its identity through security certificates, it's quite fair to ask the client to prove its identity as well. When a server provides identification as well as requiring client authentication, the authentication is called mutual authentication or two-way authentication.

Mutual authentication can be activated from web.xml by specifying the CLIENT-CERT value for the authentication method (<auth-method> element). For example, if we want to rewrite web.xml to use mutual authentication for protecting the /jsps folder and the SecureServlet through the SERVLET-CERT-ROLE role, we can do it as shown in Listing 1.

Listing 1 web.xml.

<?xml version="1.0" encoding="UTF-8"?>
<web-app version="2.5" xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee

 <display-name>Roles</display-name>

 <servlet>
  <servlet-name>SecureServlet</servlet-name>
  <servlet-class>secure.servlet.SecureServlet</servlet-class>
  <security-role-ref>
        <role-name>SERVLET-ROLE-ALIAS</role-name>
        <role-link>SERVLET-CERT-ROLE</role-link>
  </security-role-ref>
 </servlet>
 <servlet-mapping>
  <servlet-name>SecureServlet</servlet-name>
  <url-pattern>/SecureServlet</url-pattern>
 </servlet-mapping>

  <security-role>
   <role-name>SERVLET-CERT-ROLE</role-name>
 </security-role>

 <security-constraint>
    <web-resource-collection>
      <web-resource-name>Secure Servlet</web-resource-name>
      <url-pattern>/SecureServlet</url-pattern>
      <http-method>GET</http-method>
      <http-method>POST</http-method>
    </web-resource-collection>
    <auth-constraint>
      <role-name>SERVLET-CERT-ROLE</role-name>
    </auth-constraint>
    <user-data-constraint>
     <transport-guarantee>CONFIDENTIAL</transport-guarantee>
    </user-data-constraint>
 </security-constraint>

  <security-constraint>
    <web-resource-collection>
      <web-resource-name>Secure JSPs</web-resource-name>
      <url-pattern>/jsps/*</url-pattern>
      <http-method>GET</http-method>
      <http-method>POST</http-method>
    </web-resource-collection>
    <auth-constraint>
      <role-name>SERVLET-CERT-ROLE</role-name>
    </auth-constraint>
    <user-data-constraint>
     <transport-guarantee>CONFIDENTIAL</transport-guarantee>
   </user-data-constraint>
  </security-constraint>

 <login-config>
  <auth-method>CLIENT-CERT</auth-method>
  <realm-name>MyCertificateRealm</realm-name>
 </login-config>

 <welcome-file-list>
  <welcome-file>index.jsp</welcome-file>
 </welcome-file-list>

</web-app>

The SERVLET-CERT-ROLE should be mapped to a principal in sun-application.xml or sun-web.xml as follows:

<security-role-mapping>
    <role-name>SERVLET-CERT-ROLE</role-name>
    <principal-name>CN=Mike, OU=home.user, C=RO</principal-name>
    <group-name>SERVLET-CERT-USERS</group-name>
</security-role-mapping>

The <principal-name> value must correspond to the client certificate entries:

  • CN answers the question, "What is your first and last name?"
  • OU answers the question, "What is the name of your organization unit?"
  • C answers the question, "What is the two-letter country code for this unit?"

After you obtain a certificate from a certificate authority, you have to make SJSAS aware of the certificate's location, and you have to import the certificate into your browser. Mozilla.org provides details on importing certificates in Mozilla, and Microsoft provides comparable information on using digital certificates with Internet Explorer.

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