[
https://issues.apache.org/jira/browse/SHIRO-119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jared Bunting updated SHIRO-119:
--------------------------------
Attachment: shiro-oauth.patch
This is a first draft of support for the Resource Server role of OAuth 2.0. It
uses amber (which is incubated and not released), so you'll have to build and
install that before this will work. I'm mostly looking for commentary on the
design and separation of concerns. The authorization server will be coming
later - it's a much more complex piece and I'm honestly not sure if it belongs
in shiro.
> Oauth support
> -------------
>
> Key: SHIRO-119
> URL: https://issues.apache.org/jira/browse/SHIRO-119
> Project: Shiro
> Issue Type: New Feature
> Reporter: Jason Eacott
> Attachments: shiro-oauth.patch
>
>
> Create support for OAuth provider support 'out of the box'.
> This could involve a standalone provider webapp with some flexible mechanism
> 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.
-
You can reply to this email to add a comment to the issue online.
