shiro-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bdem...@apache.org
Subject [05/12] shiro-site git commit: Update what-is-shiro.md
Date Fri, 04 May 2018 19:27:31 GMT
Update what-is-shiro.md

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

Branch: refs/heads/master
Commit: f3758bd6331fed12f3ed08006ded7782d768ba31
Parents: d656e5a
Author: Olaf van der Spek <olafvdspek@gmail.com>
Authored: Fri Jan 26 15:06:19 2018 +0100
Committer: GitHub <noreply@github.com>
Committed: Fri Jan 26 15:06:19 2018 +0100

----------------------------------------------------------------------
 what-is-shiro.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/shiro-site/blob/f3758bd6/what-is-shiro.md
----------------------------------------------------------------------
diff --git a/what-is-shiro.md b/what-is-shiro.md
index 226c7d0..2fc027d 100644
--- a/what-is-shiro.md
+++ b/what-is-shiro.md
@@ -11,7 +11,7 @@ We believe:
 - Java security should be <em>really easy</em> to understand and use in your
own applications.
 - Existing Java security mechanisms (like JAAS) are too confusing and fall way short in the
area of application-level security.
 - Authentication and Authorization functionality should be as pluggable and flexible as possible.
-- Authentication and Authorization are only half of a robust security framework. Enterprise
Session Management and easy Cryptography services are the the other half.
+- Authentication and Authorization are only half of a robust security framework. Enterprise
Session Management and easy Cryptography services are the other half.
 - <b>Session Management should not be tied to web or EJB applications</b>.  We
believe Sessions are a business-tier concern that should be accessible in any client or server
environment.
 - Heterogeneous client mediums (HTTP requests, Applets, Java Web Start, C# applications,
etc) should be able to participate in the same Session, regardless of the client technology.
 - Security code should be eliminated as much as possible in favor of a cleaner declarative
security model utilizing JDK 1.5 Annotations or XML, whichever you prefer.


Mime
View raw message