SpringSource's Ben Alex Details Emerging Standards in Application Security
At JavaOne 2008 conference, Ben Alex from SpringSource talked about the emerging security requirements and standards in enterprise applications and open source frameworks that implement the standards. In the technical session, he discussed the standards like Servlet Security, Java Authentication and Authorization Service (JAAS), CAPTCHA, Single Sign-On (SSO) and Federated Identity using OpenID technology.
Ben started off the presentation with an overview of Servlet and JAAS API and the new security features in Servlet 3.0 Specification (JSR-315) such as the ability to login/logout and Self Registration. He listed the following security concerns that should be taken into consideration when designing a web application:
Component, State and Transition Security are becoming more important as the web development moves towards component-based web frameworks such as JSF, Spring Web Flow, and JBoss Seam. Spring Web Flow provides a JSF platform model and authorization of States, Flows, and Transitions. It uses Spring Security for authentication and authorization purposes. Spring Security 2 integrates with Java technology-based servlet security and JAAS software. It has a new Security Namespace as well as "Remember Me" support in the latest version.
Completely Automated Public Test to tell Computers and Humans Apart (CAPTCHA) technique is used for mitigating denial of service (DoS) and IP infringement security vulnerabilities. CAPTCHA implementation frameworks include JCaptcha and reCAPTCHA. Java platform support (MIT licensed) for reCAPTCHA is available from the Google project.
In SSO area, Spring Security supports SSO for Microsoft Windows LANs (via Samba JCIFS) and JA-SIG Central Authentication Service (CAS). Another popular technology for Federated Identity is OpenID which is currently supported by many major companies like Sun, IBM, Microsoft, Google, Yahoo, Flickr, LiveDoor, LiveJournal, Orange, and Blogger. Spring Security supports OpenID with OpenID4Java framework.
Ben also talked about advanced web security requirements like method level authorization, JSR-250 for defining method security metadata, Spring Security method metadata, and domain access control. JSR-250 (Common Annotations for the Java platform) defines the annotations like @RunAs(someRole), @RolesAllowed(someRole), @PermitAll(), @DenyAll(), @DeclareRoles(someRole) for method level authorization. These annotations can also be applied on method arguments.
The presentation also included securing web services (WS-Security), RFC-defined Basic (RFC 1945) and Digest (RFC 2617) authentication for remote client and Web 2.0 applications. Securing web services is based on WSS standard (formerly WS-Security) which provides security for SOAP messages. XWSS (part of Metro project) is a Java platform implementation of WSS. XWSS version 3.0 implements OASIS WSS Specification 1.1.
Ben talked about destination authorization when using JMS messaging in web applications. JMS 1.1 API does not provide message integrity or privacy so the JMS providers are expected to provide such features. ActiveMQ messaging framework provides three methods (read, write, and admin) for the authorization requirements. He discussed the message end-point and channel authorization and security mediation service requirements when using an Enterprise Service Bus (ESB) in Java EE applications. ESB security patterns article lists various design patterns to be considered when implementing an ESB container.
The presentation included demonstrations ranging from a simple security requirements of a web login form to implementing application security in a Google Web Toolkit (GWT) application using Spring Security framework.
Mike Amundsen May 29, 2015
Ben Linders May 28, 2015