1
0
mirror of synced 2026-08-05 09:47:05 +00:00

Fix typos in Authorization Documentation

Signed-off-by: arianna <arianna.comi03@gmail.com>
This commit is contained in:
arianna
2026-01-16 11:23:02 +01:00
committed by Josh Cummings
parent 8e9480545e
commit f1e742dfc5
2 changed files with 6 additions and 6 deletions
@@ -720,7 +720,7 @@ As a quick summary, here are the authorization rules built into the DSL:
* `hasAuthority` - The request requires that the `Authentication` have xref:servlet/authorization/architecture.adoc#authz-authorities[a `GrantedAuthority`] that matches the given value
* `hasRole` - A shortcut for `hasAuthority` that prefixes `ROLE_` or whatever is configured as the default prefix
* `hasAnyAuthority` - The request requires that the `Authentication` have a `GrantedAuthority` that matches any of the given values
* `hasAnyRole` - A shortcut for `hasAnyAuthority` that prefixes `ROLE_` or whatever is configured as the default prefix* `hasAnyAuthority` - The request requires that the `Authentication` have a `GrantedAuthority` that matches any of the given values
* `hasAnyRole` - A shortcut for `hasAnyAuthority` that prefixes `ROLE_` or whatever is configured as the default prefix
* `hasAllRoles` - A shortcut for `hasAllAuthorities` that prefixes `ROLE_` or whatever is configured as the default prefix
* `hasAllAuthorities` - The request requires that the `Authentication` have a `GrantedAuthority` that matches all of the given values
* `access` - The request uses this custom `AuthorizationManager` to determine access
@@ -1233,4 +1233,4 @@ open class SecurityConfig {
== Further Reading
Now that you have secured your application's requests, consider xref:servlet/authorization/method-security.adoc[securing its methods].
You can also read further on xref:servlet/test/index.adoc[testing your application] or on integrating Spring Security with other aspects of you application like xref:servlet/integrations/data.adoc[the data layer] or xref:servlet/integrations/observability.adoc[tracing and metrics].
You can also read further on xref:servlet/test/index.adoc[testing your application] or on integrating Spring Security with other aspects of your application like xref:servlet/integrations/data.adoc[the data layer] or xref:servlet/integrations/observability.adoc[tracing and metrics].
@@ -758,7 +758,7 @@ fun readAccountsWhenOwnedThenReturns() {
`@PostFilter` supports arrays, collections, maps, and streams (so long as the stream is still open).
For example, the above `readAccounts` declaration will function the same way as the following other three:
For example, the above `readAccounts` declaration will function the same way as the following other four:
[tabs]
======
@@ -3020,7 +3020,7 @@ void fooWhenDeniedThenReturnStars() {
@Test
void barWhenDeniedThenReturnQuestionMarks() {
String value = this.myService.foo();
String value = this.myService.bar();
assertThat(value).isEqualTo("???");
}
----
@@ -3040,7 +3040,7 @@ fun fooWhenDeniedThenReturnStars() {
@Test
fun barWhenDeniedThenReturnQuestionMarks() {
val value: String = myService.foo()
val value: String = myService.bar()
assertThat(value).isEqualTo("???")
}
----
@@ -3338,5 +3338,5 @@ class MyExpressionHandler: DefaultMethodSecurityExpressionHandler {
== Further Reading
Now that you have secured your application's requests, please xref:servlet/authorization/authorize-http-requests.adoc[secure its requests] if you haven't already.
Now that you have secured your application's methods, please xref:servlet/authorization/authorize-http-requests.adoc[secure its requests] if you haven't already.
You can also read further on xref:servlet/test/index.adoc[testing your application] or on integrating Spring Security with other aspects of you application like xref:servlet/integrations/data.adoc[the data layer] or xref:servlet/integrations/observability.adoc[tracing and metrics].