This is an automated email from the ASF dual-hosted git repository.
bmarwell pushed a commit to branch jbake
in repository https://gitbox.apache.org/repos/asf/shiro-site.git
The following commit(s) were added to refs/heads/jbake by this push:
new 13c64cf fix all other anchors.
13c64cf is described below
commit 13c64cf29b4d6f8030df7ebd42fa5b433241a7ca
Author: Benjamin Marwell <[email protected]>
AuthorDate: Fri Jan 14 22:25:53 2022 +0100
fix all other anchors.
---
jbake/content/authorization.adoc | 8 ++++----
jbake/content/realm.adoc | 4 ++--
jbake/content/session-management.adoc | 2 +-
3 files changed, 7 insertions(+), 7 deletions(-)
diff --git a/jbake/content/authorization.adoc b/jbake/content/authorization.adoc
index 56008ff..a62c755 100644
--- a/jbake/content/authorization.adoc
+++ b/jbake/content/authorization.adoc
@@ -175,7 +175,7 @@ There are few role-oriented `Subject` assertion methods you
can call, depending
|link:static/current/apidocs/org/apache/shiro/subject/Subject.html#checkRole(java.lang.String)[`checkRole(String
roleName)`] |Returns quietly if the `Subject` is assigned the specified role
or throws an `AuthorizationException` if not.
|link:static/current/apidocs/org/apache/shiro/subject/Subject.html#checkRoles(java.util.Collection)[`checkRoles(Collection<String>
roleNames)`] |Returns quietly if the `Subject` is assigned _all_ of the
specified role or throws an `AuthorizationException` if not.
-|link:static/current/apidocs/org/apache/shiro/subject/Subject.html#checkRoles(java.lang.String...)[`checkRoles(String...
roleIdentifiers)`] |Same effect as the `checkRoles` method above, but allows
Java 5 var-args style arguments.
+|link:++static/current/apidocs/org/apache/shiro/subject/Subject.html#checkRoles(java.lang.String...)++[`checkRoles(String...
roleIdentifiers)`] |Same effect as the `checkRoles` method above, but allows
Java 5 var-args style arguments.
|===
[#Authentication-AuthorizingSubjects-ProgrammaticAuthorization-PermissionBasedAuthorization]
@@ -276,8 +276,8 @@ Like the Object-based permission check methods, there are
String variants to sup
|Subject Method |Description
|link:static/current/apidocs/org/apache/shiro/subject/Subject.html#isPermitted(java.lang.String)[`isPermitted(String
perm)`] |Returns `true` if the `Subject` is permitted to perform an action or
access a resource summarized by the specified `String` permission, `false`
otherwise.
-|link:static/current/apidocs/org/apache/shiro/subject/Subject.html#isPermitted(java.util.List)[`isPermitted(String...
perms)`] |Returns an array of `isPermitted` results corresponding to the
indices in the method argument. Useful as a performance enhancement if many
`String` permission checks need to be performed (e.g. when customizing a
complex view)
-|link:static/current/apidocs/org/apache/shiro/subject/Subject.html#isPermittedAll(java.lang.String...)[`isPermittedAll(String...
perms)`] |Returns `true` if the `Subject` is permitted _all_ of the specified
`String` permissions, `false` otherwise.
+|link:static/current/apidocs/org/apache/shiro/subject/Subject.html#isPermitted(java.util.List)[`isPermitted(List
perms)`] |Returns an array of `isPermitted` results corresponding to the
indices in the method argument. Useful as a performance enhancement if many
`String` permission checks need to be performed (e.g. when customizing a
complex view)
+|link:++static/current/apidocs/org/apache/shiro/subject/Subject.html#isPermittedAll(java.lang.String...)++[`isPermittedAll(String...
perms)`] |Returns `true` if the `Subject` is permitted _all_ of the specified
`String` permissions, `false` otherwise.
|===
[#Authentication-AuthorizingSubjects-ProgrammaticAuthorization-PermissionBasedAuthorization-PermissionAssertions]
@@ -320,7 +320,7 @@ There are few permission-oriented `Subject` assertion
methods you can call, depe
|link:static/current/apidocs/org/apache/shiro/subject/Subject.html#checkPermission(org.apache.shiro.authz.Permission)[`checkPermission(Permission
p)`] |Returns quietly if the `Subject` is permitted to perform an action or
access a resource summarized by the specified `Permission` instance, or throws
an `AuthorizationException` if not.
|link:static/current/apidocs/org/apache/shiro/subject/Subject.html#checkPermission(java.lang.String)[`checkPermission(String
perm)`] |Returns quietly if the `Subject` is is permitted to perform an action
or access a resource summarized by the specified `String` permission, or throws
an `AuthorizationException` if not.
|link:static/current/apidocs/org/apache/shiro/subject/Subject.html#checkPermissions(java.util.Collection)[`checkPermissions(Collection<Permission>
perms)`] |Returns quietly if the `Subject` is permitted _all_ the specified
permissions, or throws an `AuthorizationException` if not.
-|link:static/current/apidocs/org/apache/shiro/subject/Subject.html#checkPermissions(java.lang.String...)[`checkPermissions(String...
perms)`] |Same effect as the `checkPermissions` method above, but using
`String`-based permissions.
+|link:++static/current/apidocs/org/apache/shiro/subject/Subject.html#checkPermissions(java.lang.String...)++[`checkPermissions(String...
perms)`] |Same effect as the `checkPermissions` method above, but using
`String`-based permissions.
|===
[#Authentication-AuthorizingSubjects-NotationBasedAuthorization]
diff --git a/jbake/content/realm.adoc b/jbake/content/realm.adoc
index 5b0e0fc..8b6bded 100644
--- a/jbake/content/realm.adoc
+++ b/jbake/content/realm.adoc
@@ -79,7 +79,7 @@ securityManager.realms = $blahRealm, $fooRealm, $barRealm
----
However, realize that with implicit assignment, just the order that the realms
are defined directly affects how they are consulted during authentication and
authorization attempts.
-If you change their definition order, you will change how the main
`Authenticator`'s
link:authentication.html#[[#]]#Authentication-sequence[Authentication Sequence]
functions.
+If you change their definition order, you will change how the main
`Authenticator`'s
link:authentication.html#Authentication-AuthenticationSequence[Authentication
Sequence] functions.
For this reason, and to ensure deterministic behavior, we recommend using
Explicit Assignment instead of Implicit Assignment.
@@ -88,7 +88,7 @@ For this reason, and to ensure deterministic behavior, we
recommend using Explic
Once you understand Shiro's main
link:/authentication.html#Authentication-sequence[Authentication workflow], it
is important to know exactly what happens when the `Authenticator` interacts
with a `Realm` during an authentication attempt.
-[#Realm-Supporting%7B%7BAuthenticationTokens%7D%7D]
+[#realm_supporting_authentication_Tokens]
=== Supporting `AuthenticationTokens`
As mentioned in the
link:/authentication.html#Authentication-AuthenticationSequence[authentication
sequence], just before a `Realm` is consulted to perform an authentication
attempt, its
link:static/current/apidocs/org/apache/shiro/realm/Realm.html#supports(org.apache.shiro.authc.AuthenticationToken)[`supports`]
method is called.
diff --git a/jbake/content/session-management.adoc
b/jbake/content/session-management.adoc
index b11a011..cca5e79 100644
--- a/jbake/content/session-management.adoc
+++ b/jbake/content/session-management.adoc
@@ -227,7 +227,7 @@ Then, when the `SessionManager` asks the
`EnterpriseCacheSessionDAO` to persist
[NOTE]
====
.Web Applications
-Don 't forget that assigning a *SessionDAO* is a feature when using Shiro
native SessionManager implementations. Web applications by default use a
Servlet container-based SessionManager which does not support a *SessionDAO*.
Configure a native web SessionManager as
link:#SessionManagement-websessionmanagersessiondao[explained above] if you
want to use Ehcache-based session storage in a web application.
+Don 't forget that assigning a *SessionDAO* is a feature when using Shiro
native SessionManager implementations. Web applications by default use a
Servlet container-based SessionManager which does not support a *SessionDAO*.
Configure a native web SessionManager as
link:#SessionManagement-SessionManager-Storage-EHCacheSessionDAO[explained
above] if you want to use Ehcache-based session storage in a web application.
====
[#SessionManagement-SessionManager-Storage-EHCacheSessionDAO-CacheConfiguration]
