This is an automated email from the ASF dual-hosted git repository. bdemers pushed a commit to branch jbake-authentication in repository https://gitbox.apache.org/repos/asf/shiro-site.git
commit 56ec53bdaf08f89b66597ed98be881689d62eb3e Author: Brian Demers <[email protected]> AuthorDate: Mon Nov 15 17:05:27 2021 -0500 Add missing images and removing code block from header --- .../assets/img}/ShiroAuthenticationSequence.png | Bin .../assets/img}/ShiroFeatures_Authentication.png | Bin jbake/content/authentication.adoc | 6 +++++- 3 files changed, 5 insertions(+), 1 deletion(-) diff --git a/assets/images/ShiroAuthenticationSequence.png b/jbake/assets/img/ShiroAuthenticationSequence.png similarity index 100% rename from assets/images/ShiroAuthenticationSequence.png rename to jbake/assets/img/ShiroAuthenticationSequence.png diff --git a/assets/images/ShiroFeatures_Authentication.png b/jbake/assets/img/ShiroFeatures_Authentication.png similarity index 100% rename from assets/images/ShiroFeatures_Authentication.png rename to jbake/assets/img/ShiroFeatures_Authentication.png diff --git a/jbake/content/authentication.adoc b/jbake/content/authentication.adoc index dfea5a4..e879367 100644 --- a/jbake/content/authentication.adoc +++ b/jbake/content/authentication.adoc @@ -7,6 +7,8 @@ :icons: font :toc: +image::/img/ShiroFeatures_Authentication.png[Shiro features authentication graphic, align="center"] + Authentication is the process of identity verification - that is, proving a user actually is who they say they are. For a user to prove their identity, they need to provide some identifying information as well as some sort of proof of that identity that your system understands and trusts. @@ -32,7 +34,7 @@ The username is the claimed identity, and the password is the proof matching the If a submitted password matches what is expected by the application, the application can largely assume that the user really is who they say they are because no-one else should know the same password. -== Authenticating `Subject`s +== Authenticating Subjects The process of authenticating a `Subject` can effectively broken down into three distinct steps: @@ -209,6 +211,8 @@ Now we'll cover what happens inside Shiro when an authentication attempt occurs. We've taken our previous architecture diagram from the link:/architecture.html[Architecture] chapter, and left only the components relevant to authentication highlighted. Each number represents a step during an authentication attempt: +image::/img/ShiroAuthenticationSequence.png[authentication flow diagram, align="center"] + *Step 1*: Application code invokes the `Subject.login` method, passing in the constructed `AuthenticationToken` instance representing the end-user's principals and credentials. *Step 2*: The `Subject` instance, typically a link:/static/current/apidocs/org/apache/shiro/subject/support/DelegatingSubject.html[`DelegatingSubject`] (or a subclass) delegates to the application's `SecurityManager` by calling `securityManager.login(token)`, where the actual authentication work begins.
