diff --git a/src/docbkx/springsecurity.xml b/src/docbkx/springsecurity.xml index c1816e356d..c67bc79bed 100644 --- a/src/docbkx/springsecurity.xml +++ b/src/docbkx/springsecurity.xml @@ -158,7 +158,7 @@ standards bodies such as the Internet Engineering Task Force. In addition, Spring Security provides its own set of authentication features. Specifically, Spring Security currently supports - authentication with all of these technologies: + authentication integration with all of these technologies: @@ -228,15 +228,55 @@ - Java Single Sign On (JOSSO) (integration - is provided by the JOSSO project) + Java Open Source Single Sign On (JOSSO) * - Atlassian Crowd (integration - is provided by the Atlassian Crowd product) + OpenNMS Network Management Platform * + + + + AppFuse * + + + + AndroMDA * + + + + Mule ESB * + + + + Direct Web Request (DWR) * + + + + Grails * + + + + Tapestry * + + + + JTrac * + + + + Jasypt * + + + + Roller * + + + + Elastic Plath * + + + + Atlassian Crowd * @@ -244,17 +284,21 @@ + (* Denotes provided by a third party; check our integration page + for links to the latest details) + Many independent software vendors (ISVs) adopt Spring Security - because of this rich choice of authentication models. Doing so allows - them to quickly integrate their solutions with whatever their end - clients need, without undertaking a lot of engineering or requiring - the client to change their environment. If none of the above - authentication mechanisms suit your needs, Spring Security is an open - platform and it is quite simple to write your own authentication - mechanism. Many corporate users of Spring Security need to integrate - with "legacy" systems that don't follow any particular security - standards, and Spring Security is happy to "play nicely" with such - systems. + because of this significant choice of flexible authentication models. + Doing so allows them to quickly integrate their solutions with + whatever their end clients need, without undertaking a lot of + engineering or requiring the client to change their environment. If + none of the above authentication mechanisms suit your needs, Spring + Security is an open platform and it is quite simple to write your own + authentication mechanism. Many corporate users of Spring Security need + to integrate with "legacy" systems that don't follow any particular + security standards, and Spring Security is happy to "play nicely" with + such systems. Sometimes the mere process of authentication isn't enough. Sometimes you need to also differentiate security based on the way a diff --git a/src/site/apt/index.apt b/src/site/apt/index.apt index a695ab7096..a8366fad1b 100644 --- a/src/site/apt/index.apt +++ b/src/site/apt/index.apt @@ -35,7 +35,8 @@ Key Features every web application to have its own authentication database. Nor are you restricted to single sign on across a single web container. Advanced single sign on features like proxy support and forced refresh of logins - are supported by both CAS and Spring Security. + are supported by both CAS and Spring Security. Several other SSO solutions + are also provided by third party projects, including JOSSO and CAS. * <> We use Spring application contexts for all configuration, which should help Spring developers get diff --git a/src/site/xdoc/powering.xml b/src/site/xdoc/powering.xml index 68b870f11d..6ca47e8fa7 100644 --- a/src/site/xdoc/powering.xml +++ b/src/site/xdoc/powering.xml @@ -11,6 +11,7 @@
  • JA-SIG CAS: Single Sign On system.



  • SiteMinder: Single Sign On system.



      • +
      +
    • Atlassian Crowd: Single Sign On system. Integration details.



    • A global financial institution uses Spring Security's SiteMinder integration in a physical security management application.



      • +
    • Elastic Path uses Spring Security for security.



    • A central bank that uses Spring Security for many of its internal applications with the CAS integration.



    • Several Australian Government departments use Spring Security for securing SOAP-based web services and web applications.



    • Enterprise Systems and Services at Rutgers University uses Spring Security in conjunction with JA-SIG Central Authentication Service to provide authentication and authorization capabilities to its applications including those used by staff and students as well as those utilized by web services.



      • -
    • Elastic Path uses Spring Security for security.



    • Plus many more... ;-)



      • -
    \ No newline at end of file +