forked from apache/shiro-site
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Updated site template + some content based on SEO optimization
git-svn-id: https://svn.apache.org/repos/asf/shiro/site/trunk@1562965 13f79535-47bb-0310-9956-ffa450edef68
- Loading branch information
Les Hazlewood
committed
Jan 30, 2014
1 parent
5777e66
commit 0ee3ca7
Showing
29 changed files
with
562 additions
and
329 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file was deleted.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,47 @@ | ||
title: AuthenticationFeatures-ApacheShiroAuthenticationFeatures | ||
|
||
#Apache Shiro Authentication Features | ||
|
||
Authentication is the process of identity verification-- you are trying to verify a user is who they say they are. To do so, a user needs to provide some sort of proof of identity that your system understands and trusts. | ||
|
||
The Shiro framework is designed to make authentication as clean and intuitive as possible while providing a rich set of features. Below is a highlight of the Shiro authentication features. | ||
|
||
## Features | ||
|
||
<table align="right" width="275" style="margin-left: 20px; margin-bottom: 20px; border-style: solid; border-width: 2px; border-color: navy" cellpadding="10px"> | ||
|
||
<tr> | ||
<td> | ||
<div id="border"> | ||
<h2>Related Content</h2> | ||
|
||
<h3><a href="java-authentication-guide.html">Java Authentication Guide</a></h3> | ||
<p>Learn how Authentication in Java is performed in Shiro. </br><span style="font-size:11"><a href="java-authentication-guide.html">Read More >></a></span></p> | ||
|
||
<h3><a href="authentication.html">Authentication Docs</a></h3> | ||
<p>Full documentation on Shiro's Authentication functionality. </br><span style="font-size:11"><a href="authentication.html">Read More >></a></span></p> | ||
|
||
<h3><a href="get-started.html">Getting Started</a></h3> | ||
<p>Resources, guides and tutorials for new Shiro users. </br><span style="font-size:11"><a href="get-started.html">Read More >></a></span></p> | ||
|
||
<h3><a href="webapp-tutorial.html">Web App Tutorial</a></h3> | ||
<p>Step-by-step tutorial for securing a web application with Shiro. </br><span style="font-size:11"><a href="webapp-tutorial.html">Read More >></a></span></p> | ||
|
||
</div> | ||
</td> | ||
</tr> | ||
</table> | ||
|
||
|
||
* **Subject Based** - Almost everything you do in Shiro is based on the currently executing user, called a Subject. And you can easily retrieve the Subject anywhere in your code. This makes it easier for you to understand and work with Shiro in your applications. | ||
|
||
* **Single Method call** - The authentication process is a single method call. Needing only one method call keeps the API simple and your application code clean, saving you time and effort. | ||
|
||
* **Rich Exception Hierarchy** - Shiro offers a rich exception hierarchy to offered detailed explanations for why a login failed. The hierarchy can help you more easily diagnose code bugs or customer services issues related to authentication. In addition, the richness can help you create more complex authentication functionality if needed. | ||
|
||
* **'Remember Me' built in** - Standard in the Shiro API is the ability to remember your users if they return to your application. You can offer a better user experience to your them with minimal development effort. | ||
|
||
* **Pluggable data sources** - Shiro uses pluggable data access objects (DAOs), called Realms, to connect to security data sources like LDAP and Active Directory. To help you avoid building and maintaining integrations yourself, Shiro provides out-of-the-box realms for popular data sources like LDAP, Active Directory, Kerberos, and JDBC. If needed, you can also create your own realms to support specific functionality not included in the basic realms. | ||
|
||
* **Login with one or more realms** - Using Shiro, you can easily authenticate a user against one or more realms and return one unified view of their identity. In addition, you can customize the authentication process with Shiro's notion of an authentication strategy. The strategies can be setup in configuration files so changes don't require source code modifications-- reducing complexity and maintenance effort. | ||
|
This file was deleted.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,47 @@ | ||
title: Apache Shiro Authorization Features | ||
|
||
# Apache Shiro Authorization Features | ||
|
||
Authorization, also called access control, is the process of determining access rights to resources in an application. In other words, determining "who has access to what." Authorization is used to answer security questions like, "is the user allowed to edit accounts", "is this user allowed to view this web page", "does this user have access to this button?" These are all decisions determining what a user has access to and therefore all represent authorization checks. | ||
|
||
Authorization is a critical element of any application but it can quickly become very complex. Shiro's goal is to eliminate much of the complexity around authorization so that you can more easily build secure software. Below is a highlight of the Shiro authorization features. | ||
|
||
## Features | ||
|
||
<table align="right" width="275" style="margin-left: 20px; margin-bottom: 20px; border-style: solid; border-width: 2px; border-color: navy" cellpadding="10px"> | ||
|
||
<tr> | ||
<td> | ||
<div id="border"> | ||
<h2>Related Content</h2> | ||
|
||
<h3><a href="java-authorization-guide.html">Java Authorization Guide</a></h3> | ||
<p>Learn how Shiro handles access control in Java. </br><span style="font-size:11"><a href="java-authorization-guide.html">Read More >></a></span></p> | ||
|
||
<h3><a href="authorization.html">Authorization Docs</a></h3> | ||
<p>Full documentation on Apache Shiro's Authorization functionality. </br><span style="font-size:11"><a href="authorization.html">Read More >></a></span></p> | ||
|
||
<h3><a href="get-started.html">Getting Started</a></h3> | ||
<p>Resources, guides and tutorials for new Shiro users. </br><span style="font-size:11"><a href="get-started.html">Read More >></a></span></p> | ||
|
||
<h3><a href="webapp-tutorial.html">Web App Tutorial</a></h3> | ||
<p>Step-by-step tutorial for securing a web application with Shiro. </br><span style="font-size:11"><a href="webapp-tutorial.html">Read More >></a></span></p> | ||
|
||
</div> | ||
</td> | ||
</tr> | ||
</table> | ||
|
||
* **Subject-based** - Almost everything you do in Shiro is based on the currently executing user, called a Subject. And you can easily access the subject retrieve the Subject and checks its roles, permissions, or other relevant attributes anywhere in your code. This makes it easier for you to understand and work with Shiro in your applications. | ||
|
||
* **Checks based on roles or permissions** - Since the complexity of authorization differs greatly between applications, Shiro is designed to be flexible, supporting both role-based security and permission-based security based on your projects needs. | ||
|
||
* **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** – 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, Kerboros, 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. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.