This is an automated email from the ASF dual-hosted git repository.

fpapon pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/shiro-site.git


The following commit(s) were added to refs/heads/master by this push:
     new 39bfae7  Update java-authentication-guide.md.vtl
     new 5ca699b  Merge pull request #43 from small-wei/small-wei-patch-1
39bfae7 is described below

commit 39bfae70e046f52b0f3ea40927a9324f4ea62e18
Author: small-wei <[email protected]>
AuthorDate: Tue Apr 30 15:08:52 2019 +0800

    Update java-authentication-guide.md.vtl
    
    [typo]
---
 java-authentication-guide.md.vtl | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/java-authentication-guide.md.vtl b/java-authentication-guide.md.vtl
index ed29ba4..1876d54 100644
--- a/java-authentication-guide.md.vtl
+++ b/java-authentication-guide.md.vtl
@@ -71,7 +71,7 @@ currentUser.login(token);
 
 First, we need to acquire the currently executing user, referred to as the 
subject. A subject is just a security specific view of the user----it can be a 
human, a process, cron job, doesn't matter. In Shiro, there is always a subject 
instance available to the currently executing thread. The concept of a subject 
is core to Shiro and most of the framework is centered around working with 
subjects. In this example, we will name this instance of subject currentUser.
 
-To acquire the subject, we use the 
[SecurityUtils](static/current/apidocs/org/apache/shiro/SecurityUtils.html) 
class which is also a core pat of Shiro's API. It will acquire the currently 
executing user via the 
[`getsubject()`](static/current/apidocs/org/apache/shiro/SecurityUtils.html#[[#]]#getSubject--)
 method call. And we get back a subject instance that is representing who the 
current user is who is interacting with the system. At this point in the 
example, the subject currentUser is [...]
+To acquire the subject, we use the 
[SecurityUtils](static/current/apidocs/org/apache/shiro/SecurityUtils.html) 
class which is also a core part of Shiro's API. It will acquire the currently 
executing user via the 
[`getsubject()`](static/current/apidocs/org/apache/shiro/SecurityUtils.html#[[#]]#getSubject--)
 method call. And we get back a subject instance that is representing who the 
current user is who is interacting with the system. At this point in the 
example, the subject currentUser i [...]
 
 Now with the user representation in hand, we authenticate them by just calling 
the 
[`login()`](static/current/apidocs/org/apache/shiro/subject/Subject.html#[[#]]#login-org.apache.shiro.authc.AuthenticationToken-))
 method and submit the token we just constructed a second ago.
 

Reply via email to