Apache HTTP Server

Core program features presentations from dozens of industry leaders, including Adobe Systems, Akamai, IBM, LinkedIn, NASA Jet Propulsion Laboratory, Nokia, Red Hat, SpringSource/VMWare, and Yahoo 28 June 2011—FOREST HILL, MD—The Apache ... [More] Software Foundation (ASF), the all-volunteer developers, stewards, and incubators of nearly 170 Open Source projects and initiatives, today announced "Open Source Enterprise Solutions, Cloud Computing, and Community Leadership" as the theme for ApacheCon North America. ApacheCon is the ASF's official conference, trainings, and expo, created to explore key issues in using and developing Open Source solutions "The Apache Way". This year's event takes place 7-11 November 2011 at the Westin Bayshore Vancouver, Canada, with early registration incentives available through 2 September 2011. Apache products power more than 225 million Websites (over half the Internet) and countless mission-critical applications worldwide (from financial services to publishing to radioastronomy to social networking to biomedicine research datastores to mobile medial applications). More than a dozen Apache projects form the foundation of today's Cloud computing. Five of the top 10 Open Source downloads are Apache projects: understanding their breadth and capabilities has never been more important in today's marketplace. ApacheCon brings the global Apache community together to collaborate, promote innovation, reinforce and create new connections, launch breakout technologies, and leverage opportunities in using and developing Open Source solutions. ApacheCon's professionally-directed presentations detail specific industry challenges and real-world solutions, giving attendees the must-know tips, techniques, and trends needed to stay ahead in a rapidly changing landscape. Presenters include noted members of the Apache community, as well as representatives from Adobe Systems, Akamai, Cloudera, CS Communication & Systemes, DLR (German Aerospace Center), FuseSource, Hippo, IBM, LinkedIn, Lucid Imagination, NASA Jet Propulsion Laboratory, Nokia, Nuxeo, Red Hat, Sakai Project, SpringSource/VMWare, Talend, Talis, WSO2, Yahoo, and more. Through highly relevant sessions, attendees --Open Source developers, users, enthusiasts, software architects, administrators, executives, educators, evangelists, students, and community managers-- gain first-hand insight on successfully developing, deploying, and leveraging existing and emerging Apache solutions critical to their businesses.  The ApacheCon program spans "Apache 101" basics to rocket science ("Apache in Space!"), and features countless Apache projects, from Abdera to Zookeeper. Highlights include: Open Source Enterprise Solutions: Backbone of the Web; Foundation of the Cloud; Big Data, Bigger Deployments Extending enterprise solutions to the Cloud is among the biggest strategic trends in Open Source today. The race to adoption poses its challenges across open/public, closed/private, and emerging community Clouds. The demand for reliable, highly-performant, standards-based solutions continues to grow, and Apache products are continual "go-to" options in Cloud sourcing, particularly with large scale deployments that handle terrabytes of data. Customization, security, load balancing, performance, and privacy all feature prominently in Cloud adoption, and ApacheCon's sessions address a bevy of Cloud systems, supporting data solutions, and best practices, from how to best prepare for the Cloud to ways to maximize your investment in its rapidly growing and complex ecosystem. Tracks and featured Apache projects include: Content Technologies and Data Handling (Big Data and Analytics) tracks delve into Apache projects such as Archiva, Cassandra, Chemistry, Hadoop, HBase, Jackrabbit, Jena, Lucene, Mahout, Solr, Stambol, and Tika to demonstrate: - content management at LinkedIn - managing and warehousing data repositories at the US Federal Government - developing tele-medicine solutions for smartphones - improving smart search performance up to 20,000% - relational database search solutions used by Netflix, Yelp, and StubHub - using metadata, data analysis, and semantic Web applications for machine learning - data analysis solutions as done at Yahoo, Facebook, Amazon, and eBay As Java is synonymous with the enterprise, the Enterprise and Modular Java tracks feature Apache ACE, ActiveMQ, Axis2, Camel, Celix, Karaf, ServiceMix, Zookeeper, developer-friendly Open Source Service-Oriented Applications and the pursuit of a universal OSGi. The Servers track introduces the latest improvements to the ASF’s flagship HTTP Server project and its role in Cloud environments, scaling Apache’s award-winning Tomcat and Geronimo application servers, and developing feature-rich platform as a service (PaaS) solutions. Incubating Innovation and Emerging Technologies Launched 12 years ago with the flagship Apache HTTP Server project, the ASF today develops and shepherds nearly 100 Top-Level Projects (TLPs) and 70 new initiatives in the Apache Incubator and Labs. More projects than ever have been submitted to become a part of the ASF to improve the quality of their code and participate in a larger, influential community. The ASF has successfully incubated emerging innovations such as Apache Cassandra, Apache OODT, and Apache Libcloud, as well as highly-established projects such as Apache SpamAssassin and Apache Subversion. Projects featured in the Innovation & Emerging Technologies track include Rave, Wookie, Whirr, as well as many others to be showcased in the Fast Feather Track, the popular ApacheCon attraction where attendees get a 20-minute snapshot of an array of technologies currently undergoing incubation at Apache. Opening Business, Community Leadership, and Keeping the Machine Running "Community Over Code" is an oft-repeated saying at Apache, and is reflected in ApacheCon’s Business, Community, and Infrastructure & DevOps sessions, where attendees learn best practices on enabling innovation, meritocratic leadership, managing distributed/virtual teams, driving consensus, releasing Open Source software, and community management "The Apache Way". These tracks expose the underbelly of day-to-day life in Open Source companies and communities. Technically-oriented presentations address tough questions on security and network optimization, agile vs. open development, systems integration, running data centers, and streamlining operations, and feature session topics such as Apache Maven, IPv6, performance, troubleshooting, load balancing, and more. Special Events, Public Participation ApacheCon is widely recognized as an engaging, hands-on, and interactive event, with live demos, active audience participation, ample networking opportunities, and the chance to work alongside leading members and talent in the Open Source community.  Special activities during the week include BarCampApache (7-8 November), the hands-on, unstructured, ad-hoc, participant-driven unconference; Apache Hackathon (7-8 November), where project management committee members and committers collaborate on fixing bugs, addressing issues, and adding new features to Apache code; and ASF Project MeetUps, which brings together users and developers of a particular Apache project (or area of activity) after conference hours. Both BarCampApache and ASF Project MeetUps are open to the public free of charge. ApacheCon Sponsors Cloudera (Platinum), HotWax Media and Red Hat (Gold), SpringSource (Silver), and Facebook (Bronze), are joined by community partners and exhibitors that include The Apache Software Foundation, Crowdvine, Jahia, Ning, and WSO2. Official Event Media Partners are ADMIN magazine, The Bitsource, Conferencevault, DZone, FeatherCast, Linux Pro Magazine, OSCON, OSCON Data, OSCON Java, OStatic, and ReadWriteWeb. For sponsor, exhibitor, and community partnership opportunities, contact Delia Frees at [email protected]. Registration Information ApacheCon is for everyone! Anyone interested in Apache products is welcome: ASF affiliation is not required to present at, attend, or otherwise participate in ApacheCon. Early-bird incentives include savings of up to 25% when registering by 2 September 2011. To register, visit http://apachecon.com/ and keep up with program updates by following the @ApacheCon feed on Twitter. Note to Editors Key conference message summaries and media partnerships are available. Conference registration is complimentary for members of the press with valid credentials. Contact Sally Khudairi at [email protected] for more information. About The Apache Software Foundation (ASF) Established in 1999, the all-volunteer Foundation oversees nearly one hundred fifty leading Open Source projects, including Apache HTTP Server — the world's most popular Web server software, powering more than 225 Million Websites worldwide. Through the ASF's meritocratic process known as "The Apache Way," more than 300 individual Members and 2,500 Committers successfully collaborate to develop freely available enterprise-grade software, benefiting millions of users worldwide: thousands of software solutions are distributed under the Apache License; and the community actively participates in ASF mailing lists, mentoring initiatives, and ApacheCon, the Foundation's official user conference, trainings, and expo. The ASF is a US 501(3)(c) not-for-profit charity, funded by individual donations and corporate sponsors including AMD, Basis Technology, Cloudera, Facebook, Google, IBM, HP, Matt Mullenweg, Microsoft, PSW Group, SpringSource, and Yahoo!. For more information, visit http://www.apache.org/. "Apache", "ApacheCon", and Apache Projects "ActiveMQ", "Archiva", "Axis2", "Camel", "Chemistry", "Cassandra", "Geronimo", "Hadoop", "HBase", "HTTP Server", "Jena", "Jackrabbit", "Lucene", "Mahout", "Maven", "OODT", "ServiceMix", "Stanbol", "Tika", "Tomcat", and "Zookeeper" are trademarks of The Apache Software Foundation. All other brands and trademarks are the property of their respective owners. # # # Contact: Sally Khudairi The Apache Software Foundation +1 617 921 8656 [email protected] [Less]

In the works over the past year (v2.0 was released May 2010), Apache Traffic Server v3.0.0 is the result of contributions from more than 30 developers and contributors. Technical highlights include: I. Contributions - Over 1,000 "commits" ... [More] (code, patches, or documentation written directly to the code repository); - 380+ bug tickets resolved; - 10 releases have been made during the development phase (v2.1.0 - 2.1.9) II. New features/improvements - Full 64-bit support; - Client side IPv6 support; - WCCP (Web Cache Communication Protocol); - Clustering is functional and supported (many benefits include an efficient distributed cache); - Major plug-in API improvements, making the APIs more feature rich and easier to use; - Support for many platforms, including OSX, Solaris and FreeBSD (Linux, of course, was always supported); - New improved RAM cache algorithms, for better performance and memory utilization - Many configurations are now configurable per transaction (or per mapping rule) - Many improvements in statistics and management APIs; - Multiple accept threads, and a dedicated DNS thread: - Build environment is now much more flexible, and package owner friendly; - Many, many bug fixes for improved stability and functionality. III. Performance improvements - Overall throughput is 2-3x improved over v2.0 (depending on the traffic patterns) - Response latency is up to 5x better than v2.0 - Benchmark: Serving small objects out of RAM cache, a high end server has showed over 220,000 requests / second - Benchmark: Serving small objects that are not cacheable, the same high end server could proxy 100,000 requests / second (NOTE: all benchmarks are on local network, with keep-alive) Get Involved! Apache Traffic Server downloads, documentation, mailing lists, and related resources are available at http://trafficserver.apache.org/. # # # [Less]

Highly-Performant Cloud Computing Service Serves Dynamic Content, Billions of Objects, and Terrabytes of Data for Large-Scale Deployments 14 June 2011 —FOREST HILL, MD—The Apache Software Foundation (ASF), the all-volunteer developers, stewards ... [More] , and incubators of nearly 150 Open Source projects and initiatives, today announced Apache Traffic Server v3.0.0. Apache Traffic Server is a Cloud Computing "edge" service, able to handle requests in and out of the Cloud, both by serving static content (images, JavaScript, CSS, and HTML files), and routing requests for dynamic content to a Web server (such as the Apache HTTP Server). "Traffic Server is battle hardened, serving terrabytes of data in real-life deployments where immediate content delivery is critical," said Apache Traffic Server Vice President Leif Hedstrom. "V3.0.0 builds upon that foundation, with new features and functionality, improved efficiency and performance, increased uptime, and overall easier to use.” Apache Traffic Server is a fast, scalable, and extensible HTTP/1.1 compliant caching proxy server designed to improve:  - Caching: improves response time while reducing server load and bandwidth needs by caching and reusing frequently-requested Web pages, images, and Web service calls;  - Proxying: easily add keep-alive, filter or anonymize content requests, or add load balancing by adding a proxy layer;  - Speed: scales well on modern SMP hardware, handling tens of thousands of requests per second;  - Extensibility: APIs allow for customized plug-ins, from modifying headers and content to implementing new protocol handlers;  - Reliability: successfully handles hundreds of terrabytes of data, both as forward and reverse proxies Apache Traffic Server v.3.0.0 has been benchmarked to handle more than of 200,000 requests per second -- a 277% improvement over v2.0’s already-impressive rates. Used in production in a variety of large-scale deployments, companies such as Yahoo! rely on Apache Traffic Server to handle over 400 terrabytes of traffic, and has used the project to serve more than 30 billion objects daily across its various properties including the Yahoo! homepage, and its Sports, Mail, and Finance sites. Apache Traffic Server entered the Apache Incubator in June 2009, graduated as an Apache Top-Level Project (TLP) in April 2010, and released v2.0 the following month. For technical highlights, please refer to the Apache Traffic Server v3.0.0 Features At-A-Glance at http://s.apache.org/7Or. Availability and OversightAs with all Apache products, Apache Traffic Server software is released under the Apache License v2.0, and is overseen by a self-selected team of active contributors to the project. A Project Management Committee (PMC) guides the Project’s day-to-day operations, including community development and product releases. Apache Traffic Server source code, documentation, and related resources are available at http://trafficserver.apache.org/. About The Apache Software Foundation (ASF)Established in 1999, the all-volunteer Foundation oversees nearly one hundred fifty leading Open Source projects, including Apache HTTP Server — the world's most popular Web server software. Through the ASF's meritocratic process known as "The Apache Way," more than 300 individual Members and 2,500 Committers successfully collaborate to develop freely available enterprise-grade software, benefiting millions of users worldwide: thousands of software solutions are distributed under the Apache License; and the community actively participates in ASF mailing lists, mentoring initiatives, and ApacheCon, the Foundation's official user conference, trainings, and expo. The ASF is a US 501(3)(c) not-for-profit charity, funded by individual donations and corporate sponsors including AMD, Basis Technology, Cloudera, Facebook, Google, IBM, HP, Matt Mullenweg, Microsoft, SpringSource, Talend, and Yahoo!. For more information, visit http://www.apache.org/. "Apache" and "Apache Traffic Server" are trademarks of The Apache Software Foundation. All other brands and trademarks are the property of their respective owners. # # # Media Contact: Sally Khudairi The Apache Software Foundation +1 617 921 8656 [email protected] [Less]

The Apache Software Foundation (ASF) will be holding its annual Members' meeting this July. Among the Foundation's business that takes place during this meeting is the election of new ASF Members.  At its inception in 1999, The ASF comprised 21 ... [More] individuals who oversaw the progress of the Apache HTTP Server. This group formed the Foundation's core membership. This group grew with "Committers", developers who contributed code, patches, or documentation, and were subsequently granted access by the Membership: 1) to "commit" or "write" (contribute) directly to the code repository; 2) the right to vote on community-related decisions; and 3) and the ability propose an active user for Committership. Those Committers who demonstrate merit in the Foundation’s growth, evolution, and progress are nominated for ASF Membership by existing members.  ASF Members are elected bi-annually. New Members elected at the January 2011 Members' meeting are: Greg Brown, Michael Busch, Jack Cai, Adriano Crestani, Paul Joseph Davis, Jean-Sebastien Delfino, Ted Dunning, Mohammad Nour El-Din, Julian Foad, Igor Galic, Alan Gates, Oliver Heger, Colm O Heigeartaigh, Arnaud Heritier, Jeremy Hughes, Patrick Hunt, Nandika Jayawardana, Willem Ning Jiang, Supun Kamburugamuva, Yegor Kozlov, Ken Krugler, Damitha Kumarage, Olivier Lamy, Paul Lindner, Ruwan Linton, Jimmy Lv, Rick McGuire, Mark Miller, Julien Nioche, Johan Oskarsson, Gerhard Petracek, Joerg Schaible, Theo Schlossnagle, Zoe Slattery, Stefan Sperling, Ulrich Staerk, Amila Suriarachchi, Tommaso Teofili, Tammo van Lessen, Gert Vanthienen, Igor Vaynberg, Kanchana Welagedara. Welcome all, and thank you for your contributions to the Foundation thus far! The complete list of ASF members and committers is available on people.apache.org. For more information on how the ASF works, visit http://www.apache.org/foundation/how-it-works.html. # # # [Less]

The Apache Software Foundation (ASF)'s Travel Assistance Committee (TAC) is now accepting applications for ApacheCon North America 2011, 7-11 November in Vancouver BC, Canada http://apachecon.com/. The TAC is seeking individuals from the Apache ... [More] community at-large --users, developers, educators, students, Committers, and Members-- who would like to attend ApacheCon, but need some financial support in order to be able to get there. There are limited places available, and all applicants will be scored on their individual merit. Financial assistance is available to cover flights/trains, accommodation and entrance fees either in part or in full, depending on circumstances. However, the support available for those attending only the BarCamp (7-8 November) is less than that for those attending the entire event (Conference + BarCamp 7-11 November). The Travel Assistance Committee aims to support all official ASF events, including cross-project activities; as such, it may be prudent for those in Asia and Europe to wait for an event geographically closer to them.  More information can be found at http://www.apache.org/travel/index.html including a link to the online application and detailed instructions for submitting. Applications will close on 8 July 2011 at 22:00 BST (UTC/GMT +1). The TAC team wish good luck to all those who will apply, and thank everyone in advance for tweeting, blogging, and otherwise spreading the word. # # #  [Less]

The Hama team is pleased to announce the release of Apache Hama 0.2.0-incubating under the Apache Incubator. Hama is a distributed computing framework based on BSP (Bulk Synchronous Parallel) computing techniques for massive scientific ... [More] computations. This first release includes: BSP computing framework and its examplesCLI-based managing and monitoring tool of BSP job You can be downloaded from the download page of Hama website[2]. Thanks to the Hama and Apache Incubating community for helping grow the project. 1. http://en.wikipedia.org/wiki/Bulk_synchronous_parallel 2. http://incubator.apache.org/hama/downloads.html [Less]

More Projects Than Ever Submitted to Become a Part of The Apache Software Foundation The success and reputation of The Apache Software Foundation (ASF) as one of the most influential Open Source organizations is undisputed. Launched 12 years ... [More] ago with the Apache HTTP Server, the all-volunteer ASF currently develops and shepherds nearly 170 projects, including Top-Level Projects (TLPs) and new initiatives in the Apache Incubator and Labs. Apache products power more than 203 million Websites (half the Internet!) and countless mission-critical applications worldwide. More than a dozen Apache projects form the foundation of today's Cloud computing. Five of the top 10 Open Source downloads are Apache projects. "Dozens of external projects have sought to become a part of the ASF to improve the quality of their code and participate in a larger community," explained ASF President Jim Jagielski. Incubation is the first step for a project to be considered among the diverse Open Source initiatives overseen by the ASF. A submitted project and its community will join the more than 50 projects in the Apache Incubator, and will benefit from the Foundation's widely-emulated meritocratic process, stewardship, outreach, support, community events, and guiding principles that are affectionately known as "The Apache Way". "We welcome highly-focused, emerging projects from individual contributors, as well as those with robust developer communities, global user bases, and strong corporate backing," added Jagielski. "The ASF's organizational, legal, financial, and infrastructure support gives incubating projects the ability to provide valuable software to millions of users without having to worry about liability. Today's submission of the OpenOffice.org code base is testament to our track record for successfully incubating highly-established, well-respected projects such as Apache SpamAssassin and Apache Subversion." Incubating projects (known as "podlings") benefit from hands-on mentorship from other Apache contributors and are guided on an array of processes and principles within the Foundation, including adopting the Apache voting structure and growing a vibrant and diverse community. Jim Jagielski is the proposed podling mentor for the OpenOffice.org community during the incubation process. Podlings that demonstrate that their community and products have been well-governed under the ASF's consensus-driven process, release all code under the Apache License v2.0, and fulfill the responsibilities of an incubating project move one step closer to graduation to a TLP. Upon a Project's maturation to a TLP, a Project Management Committee (PMC) is formed to guide its day-to-day operations, including community development and product releases. ASF Projects that have graduated from the Apache Incubator over the past year include Apache Cassandra, Apache Chemistry, Apache Click, Apache Libcloud, Apache OODT, Apache Shindig, Apache Traffic Server, and Apache UIMA. For more information on the Apache Incubator, please visit http://incubator.apache.org/. # # # Media Contact: Sally Khudairi +1 617 921 8656 [email protected] [Less]

This blog was written by our new committer Vladimir Ivanov who implemented a feature that users have been wanting for a long time.  In the first two parts of this blog series, scenarios were discussed where the authentication ... [More] process was performed by the container. While it often makes sense to delegate this task to the container in order to integrate with corporate services such as Single Sign-On, sometimes it might be better to take full control of the authentication process and perform this task directly in the source code. In this final part of the blog series, I'll show how to authenticate user in LDAP via the Lift API as well as introduce some changes that have been made in the authentication modules. Changes in UserAuth.scala In order to perform authentication via the Lift API, a new module LDAPAuthModule has been added. Basically, it uses the same operation sequence as the ContainerManagedAuthModule: it gets the user credentials, tries to authenticate and authorize the user, retrieves additional attributes from the LDAP for a new user and finally logs the user in. Since several operations are common to both authentication modules, it is worth placing them in a base trait LDAPBase: trait LDAPBase { LDAPBase is marked with a self-type to denote that any concrete class that mixes with this trait is a AuthModule instance   this : AuthModule => To check whether the user has a specific role, a list of roles, separated by commas, is read from the property file, split and placed into a val.   val rolesToCheck = Props.get("role_list") match {     case Full(s) => s.split(',').toList     case _ => Nil   } A new variable was also added to hold the current role for the User.   var currentRole : String = _ The object LDAPVendor and method that extracts attributes from LDAP are used by both modules and were left without changes   object myLdapVendor extends LDAPVendor   def myLdap : LDAPVendor = ...   def getAttrs(dn : String) : Map[String, List[String]] = ... The following two methods are used to construct distinguished name for the user/group pair. Since users and groups can have different bases and prefixes, specific properties are retrieved from the property file depending on the isGroup flag (The new feature, default parameters, introduced in Scala 2.8 is used to set default value for this flag).   def constructDistinguishedName(who : String, isGroup : Boolean = false) = {     val base = Props.get( if(isGroup) {"ldap.groupBase"} else {"ldap.userBase"} )  openOr ""      val dn = "%s,%s".format(constructNameWithPrefix(who, isGroup), base)      dn   }   def constructNameWithPrefix(username: String, isGroup: Boolean = false) = {     val prefix = if(isGroup) {"cn"} else {Props.get("ldap.uidPrefix") openOr ""}     val nameWithPrefix = "%s=%s".format(prefix, username)     nameWithPrefix   } The method logInUser was modified to set the current role for the authenticated User.   def logInUser(who: User) {     User.logUserIn(who)     User.setRole(currentRole)     S.notice(S.?("base_user_msg_welcome", who.niceName))   } } The singleton object ContainerManagedAuthModule now mixes with the LDAPBase trait and uses it's constructDistinguishedName method to get the LDAP attributes. In all other aspects, it has the same implementation as before. object ContainerManagedAuthModule extends AuthModule with LDAPBase ... Now let's review the new LDAPAuthModule. object LDAPAuthModule extends AuthModule with LDAPBase { At first, a set of standard methods for all authentication modules is defined:   override def isDefault = false   def loginPresentation: Box[NodeSeq] = ...   def moduleName: String = "ldap"   def createHolder() = ... The method performInit makes most of the module's work:   def performInit(): Unit = { The new module is mapped to the /ldap/login URL.     LiftRules.dispatch.append {       case Req("ldap" :: "login" :: Nil, _, PostRequest) =>         val from = S.referer openOr "/" It is necessary to check whether LDAP is enabled based on the setting in the property file and if that's the case, the user credentials are read from the HTTP request and used for the subsequent authentication in LDAP with the LDAPVendor.bindUser method. It takes the distinguished name (composed of username that comes from the HTTP request and the prefix/user base taken from the property file) and password and returns a Boolean. The next step is to check if the user is authorized with the checkRoles method.       val ldapEnabled = Props.getBool("ldap.enabled") openOr false       if(ldapEnabled) {         val name = S.param("username").map(_.trim.toLowerCase) openOr ""         val pwd = S.param("password").map(_.trim) openOr ""         if(myLdap.bindUser(constructNameWithPrefix(name), pwd) && checkRoles(constructDistinguishedName(name))) { After successful authentication and authorization, an attempt is made to find the existing User. If found, the User is logged in into the application. Otherwise, a new instance of User class is created, populated with attributes from LDAP, saved into the database and then logged in.           (for {               user <- UserAuth.find(By(UserAuth.authKey, name),                                     By(UserAuth.authType, moduleName)).flatMap(_.user.obj) or               User.find(By(User.nickname, name))             } yield user) match {             case Full(user) =>               logInUser(user)             case Empty =>               val usr = User.createAndPopulate.nickname(name).saveMe               val ldapAttrs = getAttrs(constructDistinguishedName(name))               val firstName = ldapAttrs("givenName").head               val lastName = ldapAttrs("sn").head               val mail = ldapAttrs("mail").head               usr.firstName(firstName).lastName(lastName).save               UserAuth.create.authType(moduleName).user(usr).authKey(name).save               logInUser(usr)           }         } else {           S.error(S.?("base_user_err_unknown_creds"))         }       }       S.redirectTo(from)     }   } The method checkRoles takes the username as a parameter and iterates through a list of roles defined in the property file to see whether the current role contains this name as a value of its uniqueMember attribute. If that's the case, it assign this role to the currentRole var of LDAPBase trait (it will be then saved in the HTTP session) and returns true, otherwise it returns false. def checkRoles(who : String) : Boolean = {     for (role <-rolesToCheck) {       val ldapAttrs = getAttrs(constructDistinguishedName(role, true))       val uniqueMember = ldapAttrs("uniqueMember").head       if(who == uniqueMember) {         currentRole = role         return true       }     }     return false;   } The last thing I'm going to mention are the two new properties in the default.props file. The property ldap.groupBase specifies the path in LDAP under which groups are searched. The list of application roles is set in the role_list property as a string separated by commas. default.props ;Group base DN to check whether user has specific role ldap.groupBase=ou=Groups,ou=esme,dc=lester,dc=org ;Allow access to application for following roles role_list=esme-users,monitoring-admin Note that the lift-ldap module also has to be added as a dependency to the Maven pom.xml and/or the SBT project file to work with the Lift LDAP API. Conclusion In this article, we have discovered how to authenticate the User directly in LDAP using the Lift API as well as the corresponding changes in the UserAuth class. Links Lift API: http://scala-tools.org/mvnsites/liftweb-2.3/ [Less]

Vendor-neutral, Standard Client Library Interfaces with Leading Cloud Computing Providers Including Amazon EC2, Eucalyptus, IBM Cloud, and Rackspace Cloud 25 May 2011 —FOREST HILL, MD—The Apache Software Foundation (ASF) is pleased to ... [More] announce that Apache Libcloud has graduated from the Apache Incubator as a Top-Level Project (TLP). Apache Libcloud is an Open Source Python library that provides a vendor-neutral interface to cloud provider APIs. The current version of Apache Libcloud includes backend drivers for more than twenty leading providers including Amazon EC2, Rackspace Cloud, GoGrid and Linode. Graduation signifies that both the Apache Libcloud product and community have been well-governed under the Foundation’s meritocratic, consensus-driven process and principles. "Graduation is a terrific milestone for Libcloud and will help make it a top choice for anyone looking at cloud management solutions," said Anthony Elder, ASF Vice President and Libcloud Incubation mentor. Diversification Without Vendor Lock-in Libcloud was accepted to the Apache Incubator in November 2009 with a primary focus on cloud computing functionality, and since that time has developed a strong community and preliminary support for more cloud services such as cloud storage and load-balancers as a service. With one simple API, operations teams can write once and deploy anywhere, avoiding vendor lock-in. Original Libcloud developer and Cloudkick co-founder/CEO Alex Polvi said, "I'm happy to see that Libcloud has grown into such a successful community-based Open Source project." "Our goal going forward is to support all the major cloud services offered by different providers," explained Apache Libcloud Vice President Tomaz Muraus. "Developers love the existing Libcloud interface because it is clean and easy to use and we plan to bring this simplicity and ease of use to other services such as storage and load-balancers." Apache Libcloud is used extensively in diverse production environments such as OOI Cyberinfrastructure, Cloudkick, GlobalRoute and ServerDensity. "More than half our customers use multiple cloud vendors, since adding Libcloud compatibility we've been able to more effectively support their computing aims in the cloud through cross platform compatibility," said Robert Jenkins, CTO of CloudSigma, a European IaaS provider based in Zurich, Switzerland. Availability and Oversight All Apache products are released under the Apache Software License v2.0, and are overseen by a self-selected team of active contributors to the project. Upon a Project's maturity to a TLP, a Project Management Committee (PMC) is formed to guide its day-to-day operations, including community development and product releases. Apache Libcloud source code, documentation, and related resources are available at http://libcloud.apache.org/. About The Apache Software Foundation (ASF)Established in 1999, the all-volunteer Foundation oversees nearly one hundred fifty leading Open Source projects, including Apache HTTP Server — the world's most popular Web server software. Through the ASF's meritocratic process known as "The Apache Way," more than 300 individual Members and 2,500 Committers successfully collaborate to develop freely available enterprise-grade software, benefiting millions of users worldwide: thousands of software solutions are distributed under the Apache License; and the community actively participates in ASF mailing lists, mentoring initiatives, and ApacheCon, the Foundation's official user conference, trainings, and expo. The ASF is a US 501(3)(c) not-for-profit charity, funded by individual donations and corporate sponsors including AMD, Basis Technology, Cloudera, Facebook, Google, IBM, HP, Matt Mullenweg, Microsoft, SpringSource, Talend, and Yahoo!. For more information, visit http://www.apache.org/. "Apache" and "Apache Libcloud" are trademarks of The Apache Software Foundation. All other brands and trademarks are the property of their respective owners. # # # Contact: Sally Khudairi The Apache Software Foundation +1 617 921 8656 [email protected] [Less]

A New Logo for Apache OpenWebBeans! The Apache OpenWebBeans community has voted on a new Logo recently and is happy to announce the winner today: We'd like to say thanks to Adonis Raduca for doing this excellent design and ... [More] especially thank Irian (yea those excellent bunch of folks who originally wrote and donated Apache MyFaces)for covering the expenses of the new logo design! [Less]