From 2440dd42ae573f8b5e602230189e55fefab0c513 Mon Sep 17 00:00:00 2001 From: Mohammed Fadhil Date: Tue, 26 Nov 2024 09:09:09 +0300 Subject: [PATCH 1/2] Fix phrasing for clarity in the docs. --- docs/modules/ROOT/pages/prerequisites.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/modules/ROOT/pages/prerequisites.adoc b/docs/modules/ROOT/pages/prerequisites.adoc index b1e3993c730..8ad59654189 100644 --- a/docs/modules/ROOT/pages/prerequisites.adoc +++ b/docs/modules/ROOT/pages/prerequisites.adoc @@ -4,7 +4,7 @@ Spring Security requires a Java 17 or higher Runtime Environment. As Spring Security aims to operate in a self-contained manner, you do not need to place any special configuration files in your Java Runtime Environment. -In particular, you need not configure a special Java Authentication and Authorization Service (JAAS) policy file or place Spring Security into common classpath locations. +In particular, you do not need to configure a special Java Authentication and Authorization Service (JAAS) policy file or place Spring Security in common classpath locations. Similarly, if you use an EJB Container or Servlet Container, you need not put any special configuration files anywhere nor include Spring Security in a server classloader. All the required files are contained within your application. From 7f468f0a5d13465f74fe8c18fdd0663d77e9dccb Mon Sep 17 00:00:00 2001 From: Mohammed Fadhil Date: Tue, 26 Nov 2024 09:24:26 +0300 Subject: [PATCH 2/2] Fix phrasing for clarity in the docs. --- docs/modules/ROOT/pages/prerequisites.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/modules/ROOT/pages/prerequisites.adoc b/docs/modules/ROOT/pages/prerequisites.adoc index 8ad59654189..d22cf6907be 100644 --- a/docs/modules/ROOT/pages/prerequisites.adoc +++ b/docs/modules/ROOT/pages/prerequisites.adoc @@ -6,7 +6,7 @@ Spring Security requires a Java 17 or higher Runtime Environment. As Spring Security aims to operate in a self-contained manner, you do not need to place any special configuration files in your Java Runtime Environment. In particular, you do not need to configure a special Java Authentication and Authorization Service (JAAS) policy file or place Spring Security in common classpath locations. -Similarly, if you use an EJB Container or Servlet Container, you need not put any special configuration files anywhere nor include Spring Security in a server classloader. +Similarly, if you use an EJB Container or Servlet Container, you do not need to put any special configuration files anywhere nor include Spring Security in a server classloader. All the required files are contained within your application. This design offers maximum deployment time flexibility, as you can copy your target artifact (be it a JAR, WAR, or EAR) from one system to another and it immediately works.