Mailing-List: contact dev-help@shiro.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@shiro.apache.org
Date: Sat, 11 Apr 2015 08:39:12 +0000 (UTC)
From: =?utf-8?Q?Jan_H=C3=B8ydahl_=28JIRA=29?= <jira@apache.org>
To: dev@shiro.apache.org
Message-ID: <JIRA.12721381.1402914270000.62593.1428741552284@Atlassian.JIRA>
In-Reply-To: <JIRA.12721381.1402914270000@Atlassian.JIRA>
References: <JIRA.12721381.1402914270000@Atlassian.JIRA>
 <JIRA.12721381.1402914270082@arcas>
Subject: [jira] [Commented] (SHIRO-507) Website Features wrong - Kerberos
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/SHIRO-507?page=3Dcom.atlassian.=
jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D14490=
869#comment-14490869 ]=20

Jan H=C3=B8ydahl commented on SHIRO-507:
-----------------------------------

[~lhazlewood], time to fix the home page after 3-4 years in error?

Even better, add Kerberos support, but seems all committers have left the p=
roject???

> 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 dat=
asource, which is wrong, as [SHIRO-499|https://issues.apache.org/jira/brows=
e/SHIRO-499] shows.
> Here is just a quick fix:
> {code}
> $ svn diff
> Index: authentication-features.md
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> --- authentication-features.md  (Revision 1602834)
> +++ authentication-features.md  (Arbeitskopie)
> @@ -41,7 +41,7 @@
> =20
>  *   **'Remember Me' built in** - Standard in the Shiro API is the abilit=
y to remember your users if they return to your application.  You can offer=
 a better user experience to your them with minimal development effort.
> =20
> -*   **Pluggable data sources** - Shiro uses pluggable data access object=
s (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 lik=
e LDAP, Active Directory, Kerberos, and JDBC.  If needed, you can also crea=
te your own realms to support specific functionality not included in the ba=
sic realms.
> +*   **Pluggable data sources** - Shiro uses pluggable data access object=
s (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 lik=
e LDAP, Active Directory and JDBC.  If needed, you can also create your own=
 realms to support specific functionality not included in the basic realms.
> =20
>  *   **Login with one or more realms** - Using Shiro, you can easily auth=
enticate a user against one or more realms and return one unified view of t=
heir identity.  In addition, you can customize the authentication process w=
ith Shiro's notion of an authentication strategy. The strategies can be set=
up in configuration files so changes don't require source code modification=
s-- reducing complexity and maintenance effort.
> {code}


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)