shiro-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bdem...@apache.org
Subject [07/12] shiro-site git commit: small typos
Date Thu, 22 Jun 2017 20:11:19 GMT
small typos

Fixes: #18


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

Branch: refs/heads/master
Commit: 38619b0a498ae348c572bdc85fcedf323ab7632b
Parents: bd3ab51
Author: Jens Piegsa <piegsa@gmail.com>
Authored: Wed May 10 11:30:39 2017 +0200
Committer: Brian Demers <bdemers@apache.org>
Committed: Thu Jun 22 16:10:44 2017 -0400

----------------------------------------------------------------------
 authorization-features.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/shiro-site/blob/38619b0a/authorization-features.md
----------------------------------------------------------------------
diff --git a/authorization-features.md b/authorization-features.md
index cf0eb88..99eac94 100644
--- a/authorization-features.md
+++ b/authorization-features.md
@@ -14,11 +14,11 @@ Authorization is a critical element of any application but it can quickly
become
 
 *   **Powerful and intuitive permission syntax** - As an option, Shiro provides an out-of-the-box
permission syntax, called Wildcard Permissions, that help you model the fine grained access
policies your application may have. By using Shiro's Wildcard Permissions you get an easy-to-process
and human readable syntax.  Moreoever, you don't have to go through the time-consuming effort
and complexity of creating your own method for representing your access policies.
 
-*   **Multiple enforcement options** &#8211; Authorization checks in Shiro can be done
through in-code checks, JDK 1.5 annotations, AOP, and JSP/GSP Taglibs.  Shiro's goal is to
give you the choice to use the option you think are best based on your preferences and project
needs.
+*   **Multiple enforcement options** - Authorization checks in Shiro can be done through
in-code checks, JDK 1.5 annotations, AOP, and JSP/GSP Taglibs.  Shiro's goal is to give you
the choice to use the option you think are best based on your preferences and project needs.
 
 *   **Strong caching support** - Any of the modern open-source and/or enterprise caching
products can be plugged in to Shiro to provide a fast and efficient user-experience. For authorization,
caching is crucial for performance in larger environments or with more complex policies using
back-end security data sources.
 
-*   **Pluggable data sources** - Shiro uses pluggable data access objects, referred to as
Realms, to connect to security data sources where you keep your access control information,
like a LDAP or a relational database.  To help you avoid building and maintaining integrations
yourself, Shiro provides out-of-the-box realms for popular data sources like LDAP, Active
Directory, and JDBC.  If needed, you can also create your own realms to support specific functionality
not included in the basic realms.
+*   **Pluggable data sources** - Shiro uses pluggable data access objects, referred to as
Realms, to connect to security data sources where you keep your access control information,
like an LDAP server or a relational database.  To help you avoid building and maintaining
integrations yourself, Shiro provides out-of-the-box realms for popular data sources like
LDAP, Active Directory, and JDBC.  If needed, you can also create your own realms to support
specific functionality not included in the basic realms.
 
-*   **Supports any data model** - Shiro can support any data model for access control-- it
doesn't force a model on you. Your realm implementation ultimately decides how your permissions
and roles are grouped together and whether to return a "yes" or a "no" answer to Shiro.  This
feature allows you to architect your application in the manner you chose and Shiro will bend
to support you.
+*   **Supports any data model** - Shiro can support any data model for access control&#8212;it
doesn't force a model on you. Your realm implementation ultimately decides how your permissions
and roles are grouped together and whether to return a "yes" or a "no" answer to Shiro.  This
feature allows you to architect your application in the manner you chose and Shiro will bend
to support you.
 <input type="hidden" id="ghEditPage" value="authorization-features.md"></input>


Mime
View raw message