Mailing-List: contact dev-help@shiro.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@shiro.apache.org
Date: Sun, 26 Feb 2012 08:39:50 +0000 (UTC)
From: =?utf-8?Q?J=C3=A9r=C3=B4me_Leleu_=28Updated=29_=28JIRA=29?=
 <jira@apache.org>
To: dev@shiro.apache.org
Message-ID: 
 <622959230.20678.1330245590808.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (SHIRO-119) Oauth support
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


     [ https://issues.apache.org/jira/browse/SHIRO-119?page=3Dcom.atlassian=
.jira.plugin.system.issuetabpanels:all-tabpanel ]

J=C3=A9r=C3=B4me Leleu updated SHIRO-119:
-------------------------------

    Attachment: shiro-oauth-svn.patch

new patch with some minor updates
               =20
> Oauth support
> -------------
>
>                 Key: SHIRO-119
>                 URL: https://issues.apache.org/jira/browse/SHIRO-119
>             Project: Shiro
>          Issue Type: New Feature
>            Reporter: Jason Eacott
>            Assignee: Kalle Korhonen
>         Attachments: shiro-oauth-documentation.pdf, shiro-oauth-svn.patch=
, shiro-oauth.patch
>
>
> Create support for OAuth provider  support 'out of the box'.=20
> This could involve a standalone provider webapp with some flexible mechan=
ism for data storage, and/or remote data retrieval & management,
> and a customisable way to integrate application/transport specific OAuth =
based authentication with Shiro (HTTP/XMPP etc).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrato=
rs: https://issues.apache.org/jira/secure/ContactAdministrators!default.jsp=
a
For more information on JIRA, see: http://www.atlassian.com/software/jira