This is an automated email from the ASF dual-hosted git repository.
bmarwell pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/shiro-site.git
The following commit(s) were added to refs/heads/main by this push:
new 8f47d2916 [LINKS] authorization.adoc images fix
new 2ba8b29e8 Merge pull request #166 from bmarwell/authz_img_fix
8f47d2916 is described below
commit 8f47d29169ead3d61b030c9973e58b7ec3179374
Author: Benjamin Marwell <[email protected]>
AuthorDate: Sun Jul 24 13:38:21 2022 +0200
[LINKS] authorization.adoc images fix
---
src/site/content/authorization.adoc | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/src/site/content/authorization.adoc
b/src/site/content/authorization.adoc
index e5b3ec91f..3842c8ee9 100644
--- a/src/site/content/authorization.adoc
+++ b/src/site/content/authorization.adoc
@@ -8,7 +8,7 @@
:icons: font
:toc:
-image::/img/ShiroFeatures_Authorization.png[Shiro features authorization
graphic, align="center"]
+image::/images/ShiroFeatures_Authorization.png[Shiro features authorization
graphic, align="center"]
Authorization, also known as _access control_, is the process of managing
access to resources. In other words, controlling _who_ has access to _what_ in
an application.
@@ -508,7 +508,7 @@ Shiro offers a Tag Library for controlling JSP/GSP page
output based on `Subject
[#Authentication-AuthorizingSequence]
== Authorization Sequence
-image::/img/ShiroAuthorizationSequence.png[Shiro authorization sequence
graphic, align="center"]
+image::/images/ShiroAuthorizationSequence.png[Shiro authorization sequence
graphic, align="center"]
Now that we've seen how to perform authorization based on the current
`Subject`, let's take a look at what happens inside Shiro whenever an
authorization call is made.
