This site is the archived OWASP Foundation Wiki and is no longer accepting Account Requests.
To view the new OWASP Foundation website, please visit https://owasp.org
Difference between revisions of "Java server (J2EE) code review"
(→Servlet Authentication) |
(→Servlet Authentication) |
||
Line 14: | Line 14: | ||
During the course of Servlet processing, the HttpServlet.service() method is called before the "do" methods (doGet(), doPost(), etc.) therefore no significant processing should be placed in HttpServlet.service() prior to validating that the correct HTTP method was used to submit the transaction. Therefored is prudent to examine that the correct http method (doPost(), doGet() has been over-ridden as opposed to service() method. | During the course of Servlet processing, the HttpServlet.service() method is called before the "do" methods (doGet(), doPost(), etc.) therefore no significant processing should be placed in HttpServlet.service() prior to validating that the correct HTTP method was used to submit the transaction. Therefored is prudent to examine that the correct http method (doPost(), doGet() has been over-ridden as opposed to service() method. | ||
+ | |||
+ | In the case of an authentication servlet is would be recommende to assure that the doGet() method has been overridden. | ||
+ | |||
+ | One solution to prevent HTTP GET requqests is to use the HTTPServletRequest.getMethod() to examine if the methods is POST. | ||
==J2EE Authorisation Technologies== | ==J2EE Authorisation Technologies== |
Revision as of 11:29, 15 March 2007
Introduction
Java EE Authentication Technologies
The Java EE framework contains a number of options from an authentication standpoint, such as,
- Java Authentication and Authorization Service (JAAS)
- Java Secure Socket Extensions (JSSE.)
- Authentication and key exchange (RSA & DSA), SSL Authentication
- Java 2 Security Model
Servlet Authentication
The Java API javax.servlet.HttpServlet contains a number of methods to receive HTTP requests. One fundimental practice in application security is not to hue HTTP GET during the authentication sequence (This is because sensitive credentials may be logged inadvertantly on the web server). HttpServlet harbours methods such as doPost(), doPut(), doDelete(), doGet() to name a few. These methods can be used to process incomming HTTP requests.
During the course of Servlet processing, the HttpServlet.service() method is called before the "do" methods (doGet(), doPost(), etc.) therefore no significant processing should be placed in HttpServlet.service() prior to validating that the correct HTTP method was used to submit the transaction. Therefored is prudent to examine that the correct http method (doPost(), doGet() has been over-ridden as opposed to service() method.
In the case of an authentication servlet is would be recommende to assure that the doGet() method has been overridden.
One solution to prevent HTTP GET requqests is to use the HTTPServletRequest.getMethod() to examine if the methods is POST.