Spring Security began in late 2003 as "The Acegi Security System for Spring". A question was posed on the Spring Developers' mailing list asking whether there had been any consideration given to a Spring-based security implementation. At the time the Spring community was relatively small (especially compared with the size today!), and indeed Spring itself had only existed as a SourceForge project from early 2003. The response to the question was that it was a worthwhile area, although a lack of time currently prevented its exploration.

Spring Security於2003年底開始作為“Acegi安全系統的春天”。在Spring Developers的郵件列表中提出了一個問題，詢問是否對基於Spring的安全實現給予了任何考慮。當時Spring社群相對較小（特別是與今天的大小相比！），而且Spring本身從2003年初開始只作為SourceForge專案存在。對這個問題的回答是，它是一個值得的區域，儘管缺乏時間目前阻止了它的探索。   With that in mind, a simple security implementation was built and not released. A few weeks later another member of the Spring community inquired about security, and at the time this code was offered to them. Several other requests followed, and by January 2004 around twenty people were using the code. These pioneering users were joined by others who suggested a SourceForge project was in order, which was duly established in March 2004.   考慮到這一點，構建了一個簡單的安全實現，但未釋出。幾周後，Spring社群的另一名成員詢問了安全性，當時這個程式碼已經提供給他們。隨後還有其他幾個請求，到2004年1月，大約有20個人正在使用該程式碼。這些開拓性的使用者加入了其他人，他們建議訂購SourceForge專案，該專案於2004年3月正式成立。   In those early days, the project didn’t have any of its own authentication modules. Container Managed Security was relied upon for the authentication process, with Acegi Security instead focusing on authorization. This was suitable at first, but as more and more users requested additional container support, the fundamental limitation of container-specific authentication realm interfaces became clear. There was also a related issue of adding new JARs to the container’s classpath, which was a common source of end user confusion and misconfiguration.   在那些早期，該專案沒有任何自己的身份驗證模組。容器管理安全性依賴於身份驗證過程，而Acegi Security則專注於授權。這在一開始是合適的，但隨著越來越多的使用者請求額外的容器支援，容器特定的身份驗證領域介面的基本限制變得清晰。還有一個相關的問題是將新的JAR新增到容器的類路徑中，這是終端使用者混淆和配置錯誤的常見原因。   Acegi Security-specific authentication services were subsequently introduced. Around a year later, Acegi Security became an official Spring Framework subproject. The 1.0.0 final release was published in May 2006 - after more than two and a half years of active use in numerous production software projects and many hundreds of improvements and community contributions.   隨後引入了Acegi Security特定的身份驗證服務。大約一年後，Acegi Security成為Spring Framework的正式子專案。 1.0.0最終版本於2006年5月釋出 - 經過兩年半的積極使用，在眾多生產軟體專案和數百項改進和社群貢獻中。   Acegi Security became an official Spring Portfolio project towards the end of 2007 and was rebranded as "Spring Security".   Acegi Security於2007年底成為正式的Spring Portfolio專案，並更名為“Spring Security”。   Today Spring Security enjoys a strong and active open source community. There are thousands of messages about Spring Security on the support forums. There is an active core of developers who work on the code itself and an active community which also regularly share patches and support their peers.   今天，Spring Security擁有一個強大而活躍的開源社群。在支援論壇上有成千上萬的關於Spring Security的訊息。有一個活躍的開發人員核心，他們致力於程式碼本身和一個活躍的社群，它也定期共享補丁並支援他們的同行。