shiro-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bdem...@apache.org
Subject shiro-site git commit: Fix typo Fixes: #9
Date Tue, 24 Jan 2017 16:01:20 GMT
Repository: shiro-site
Updated Branches:
  refs/heads/master 748b73a6e -> 0587e9808


Fix typo
Fixes: #9


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

Branch: refs/heads/master
Commit: 0587e9808a68beada6f8b6fcd6d6c574a0fbdd7a
Parents: 748b73a
Author: Adam Kulcsar <kulcsar.adam1991@gmail.com>
Authored: Tue Jan 24 14:44:06 2017 +0100
Committer: Brian Demers <bdemers@apache.org>
Committed: Tue Jan 24 11:00:15 2017 -0500

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


http://git-wip-us.apache.org/repos/asf/shiro-site/blob/0587e980/authentication.md.vtl
----------------------------------------------------------------------
diff --git a/authentication.md.vtl b/authentication.md.vtl
index 02f697b..289bf36 100644
--- a/authentication.md.vtl
+++ b/authentication.md.vtl
@@ -225,7 +225,7 @@ An AuthenticationStrategy is a stateless component that is consulted 4
times dur
 3.  immediately after an an individual Realm's `getAuthenticationInfo` method is called
 4.  after all of the Realms have been invoked
 
-Also an `AuthenticationStrategy` is responsible for aggregating the results from each successful
Realm and 'bundling' them into a single [`AuthenticationInfo`](static/current/apidocs/org/apache/shiro/authc/AuthenticationInfo.html)
representation. This final aggregate `AuthenticatinoInfo` instance is what is returned by
the `Authenticator` instance and is what Shiro uses to represent the `Subject`'s final identity
(aka Principals).
+Also an `AuthenticationStrategy` is responsible for aggregating the results from each successful
Realm and 'bundling' them into a single [`AuthenticationInfo`](static/current/apidocs/org/apache/shiro/authc/AuthenticationInfo.html)
representation. This final aggregate `AuthenticationInfo` instance is what is returned by
the `Authenticator` instance and is what Shiro uses to represent the `Subject`'s final identity
(aka Principals).
 
 #info("Subject Identity 'View'", "If you use more than one Realm in your application to acquire
account data from multiple data sources, the <code>AuthenticationStrategy</code>
is ultimately responsible for the final 'merged' view of the Subject's identity that is seen
by the application.")
 


Mime
View raw message