Robert Kornmesser created SHIRO-507:
---------------------------------------
Summary: Website Features wrong - Kerberos
Key: SHIRO-507
URL: https://issues.apache.org/jira/browse/SHIRO-507
Project: Shiro
Issue Type: Improvement
Components: Web, Web Site
Reporter: Robert Kornmesser
Priority: Minor
The Feature Page still announces Kerberos as out-of-the-box pluggable
datasource, which is wrong, as
[SHIRO-499|https://issues.apache.org/jira/browse/SHIRO-499] shows.
Here is just a quick fix:
{code}
$ svn diff
Index: authentication-features.md
===================================================================
--- authentication-features.md (Revision 1602834)
+++ authentication-features.md (Arbeitskopie)
@@ -41,7 +41,7 @@
* **'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.
+* **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 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.
{code}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
