shiro-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bdem...@apache.org
Subject [2/2] shiro-site git commit: replace html entity with apostroph
Date Thu, 12 Jan 2017 15:41:45 GMT
replace html entity with apostroph

Fixes: #6


Project: http://git-wip-us.apache.org/repos/asf/shiro-site/repo
Commit: http://git-wip-us.apache.org/repos/asf/shiro-site/commit/f9fffecb
Tree: http://git-wip-us.apache.org/repos/asf/shiro-site/tree/f9fffecb
Diff: http://git-wip-us.apache.org/repos/asf/shiro-site/diff/f9fffecb

Branch: refs/heads/master
Commit: f9fffecb52a18c661999646d4deadaaf58088e7c
Parents: e9543b4
Author: alexcom <a.kravec84@gmail.com>
Authored: Thu Jan 12 16:22:39 2017 +0200
Committer: Brian Demers <bdemers@apache.org>
Committed: Thu Jan 12 10:32:52 2017 -0500

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


http://git-wip-us.apache.org/repos/asf/shiro-site/blob/f9fffecb/java-authentication-guide.md.vtl
----------------------------------------------------------------------
diff --git a/java-authentication-guide.md.vtl b/java-authentication-guide.md.vtl
index 323caf8..878b187 100644
--- a/java-authentication-guide.md.vtl
+++ b/java-authentication-guide.md.vtl
@@ -69,7 +69,7 @@ Subject currentUser = SecurityUtils.getSubject();
 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&\#8217;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.
+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 anonymous. There is no identity associated with them.
 


Mime
View raw message