You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/src/docs/upgrading/upgrading7x.adoc
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -17,18 +17,18 @@ specific language governing permissions and limitations
17
17
under the License.
18
18
////
19
19
20
-
===Upgrading to 7.x (from Grails 6 / Spring Security 5.x)
20
+
== Upgrading to 7.x (from Grails 6 / Spring Security 5.x)
21
21
22
22
This guide covers upgrading the Grails Spring Security plugins from the Grails 6.x era (plugin versions 5.x/6.x, Spring Security 5.8.x) to the Grails 7.x era (plugin version 7.x, Spring Security 6.x).
23
23
24
24
For the full Grails framework upgrade guide (Java 17 baseline, Groovy 4, coordinate changes, Gradle updates, etc.), see the https://docs.grails.org/7.0.x/guide/upgrading.html[Grails 7 Upgrade Guide].
25
25
26
-
==== Repository Consolidation
26
+
=== Repository Consolidation
27
27
28
28
The previously separate Spring Security plugin repositories have been consolidated into a single mono-repository: https://github.com/apache/grails-spring-security[apache/grails-spring-security].
29
29
This repository now contains the core plugin and all extension plugins (ACL, CAS, LDAP, OAuth2, REST, and UI).
30
30
31
-
==== Dependency Changes
31
+
=== Dependency Changes
32
32
33
33
All artifacts have moved to the `org.apache.grails` group.
34
34
The most notable change is that `spring-security-core` has been renamed to `grails-spring-security` (dropping the `-core` suffix).
@@ -73,7 +73,7 @@ Update your `build.gradle` dependencies as follows:
NOTE: With the unified Grails BOM, versions are managed automatically when using a Grails Gradle plugin.
91
91
You no longer need to specify the version explicitly.
92
92
93
-
==== REST Plugin Token Storage Submodules
93
+
=== REST Plugin Token Storage Submodules
94
94
95
95
If you use the Spring Security REST plugin with a specific token storage backend, note the following renames:
96
96
@@ -99,7 +99,7 @@ If you use the Spring Security REST plugin with a specific token storage backend
99
99
* `spring-security-rest-memcached` is now `grails-spring-security-rest-memcached`
100
100
* `spring-security-rest-redis` is now `grails-spring-security-rest-redis`
101
101
102
-
==== Spring Security 6.x Changes
102
+
=== Spring Security 6.x Changes
103
103
104
104
The underlying Spring Security framework has been upgraded from 5.8.x to 6.x.
105
105
Key changes that may affect your application:
@@ -108,7 +108,7 @@ Key changes that may affect your application:
108
108
* **Security filter chain configuration**: The `WebSecurityConfigurerAdapter` has been removed in Spring Security 6. If you have custom security configurations extending this class, you will need to migrate to the component-based approach. The Grails Spring Security plugin handles the core filter chain configuration internally, but any custom Spring Security beans may need updating.
109
109
* **Default security behaviors**: Some default behaviors have changed in Spring Security 6 (e.g., CSRF protection, session management). Review the https://docs.spring.io/spring-security/reference/migration-7/index.html[Spring Security reference documentation] for the complete list of changes.
110
110
111
-
==== Automated Migration
111
+
=== Automated Migration
112
112
113
113
The coordinate rename script from the Grails core repository also handles Spring Security artifacts.
114
114
Running it will update your Gradle files automatically:
@@ -120,7 +120,7 @@ Running it will update your Gradle files automatically:
120
120
121
121
The script is located in the `etc/bin` directory of the https://github.com/apache/grails-core/tree/7.0.x/etc/bin[grails-core] repository.
122
122
123
-
==== Configuration Compatibility
123
+
=== Configuration Compatibility
124
124
125
125
The `grails.plugin.springsecurity.*` configuration namespace remains unchanged.
126
126
Your existing `application.groovy` or `application.yml` security configuration should work without modification after updating the dependencies.
Copy file name to clipboardExpand all lines: plugin-acl/docs/src/docs/introduction.adoc
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -24,6 +24,6 @@ The ACL plugin adds Domain Object Security support to a Grails application that
24
24
25
25
The core plugin and other extension plugins support restricting access to URLs via rules that include checking a user's authentication status, roles, etc. and the ACL plugin extends this by adding support for restricting access to individual domain class instances. The access can be very fine-grained and can define which actions can be taken on an object - these typically include Read, Create, Write, Delete, and Administer but you're free to define whatever actions you like.
26
26
27
-
To learn about using ACLs in Grails, you can follow the <<tutorial>> and in addition you can download and run a complete Grails application that uses the plugin. Installing and running the application are described in <<sampleApp>>.
27
+
To learn about using ACLs in Grails, you can follow the <<acl-tutorial>> and in addition you can download and run a complete Grails application that uses the plugin. Installing and running the application are described in <<acl-sampleApp>>.
28
28
29
29
In addition to this document, you should read the https://docs.spring.io/spring-security/reference/servlet/authorization/acls.html[Spring Security documentation].
Copy file name to clipboardExpand all lines: plugin-acl/docs/src/docs/tutorial.adoc
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -51,7 +51,7 @@ This will transitively install the https://github.com/apache/grails-spring-secur
51
51
$ grails s2-quickstart com.testacl User Role
52
52
....
53
53
54
-
The ACL support uses domain classes and includes them in the JAR file, but to allow customizing them (e.g. to enable Hibernate 2^nd^-level caching) there's a script that copies the domain classes into your application, <<s2-create-acl-domains>>. There's no need to run this script if the default configuration is sufficient.
54
+
The ACL support uses domain classes and includes them in the JAR file, but to allow customizing them (e.g. to enable Hibernate 2^nd^-level caching) there's a script that copies the domain classes into your application, <<acl-s2-create-acl-domains>>. There's no need to run this script if the default configuration is sufficient.
55
55
56
56
Note that you cannot change the domain class names or packages since the plugin references them by name. Grails allows you to override plugin artifacts by creating (or copying and modifying existing) classes with the same name and package in your application.
Copy file name to clipboardExpand all lines: plugin-acl/docs/src/docs/usage/domainClasses.adoc
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -22,7 +22,7 @@ under the License.
22
22
23
23
The plugin uses domain classes to manage database state. Ordinarily the database structure isn't all that important, but to be compatible with the traditional JDBC-based Spring Security code, the domain classes are configured to generate the table and column names that are used there.
24
24
25
-
The plugin classes related to persistence use these classes, so they're included in the plugin but can be overridden by running the <<s2-create-acl-domains>> script.
25
+
The plugin classes related to persistence use these classes, so they're included in the plugin but can be overridden by running the <<acl-s2-create-acl-domains>> script.
26
26
27
27
As you can see, the database structure is highly normalized.
Copy file name to clipboardExpand all lines: plugin-core/docs/src/docs/authentication/rememberMeCookie.adoc
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -92,4 +92,4 @@ The remember-me cookie is very secure, but for an even stronger solution you can
92
92
93
93
Persistent login is also useful for authentication schemes like Facebook, where you do not manage passwords in your database, but most of the other user information is stored locally. Without a password you cannot use the standard cookie format, so persistent logins enable remember-me cookies in these scenarios.
94
94
95
-
To use this feature, run the <<s2-create-persistent-token>> script. This will create the domain class, and register its name in `grails-app/conf/application.groovy`. It will also enable persistent logins by setting `rememberMe.persistent` to `true`.
95
+
To use this feature, run the <<core-s2-create-persistent-token>> script. This will create the domain class, and register its name in `grails-app/conf/application.groovy`. It will also enable persistent logins by setting `rememberMe.persistent` to `true`.
0 commit comments