Have you read this?
http://shiro.apache.org/web.html

BTW Stormpath is an easy way to go, no need to set up users, worry about 
encryption etc. in your own database.

On Jun 2, 2015, at 1:02 PM, David Hoffer wrote:

> Thanks for the replies.  Although I might not gain a lot using Shiro for my 
> use case, one benefit I see is that then I can manage users in the app 
> instead of via the container...which would be helpful.
> 
> Can someone point me to a basic example of replacing container managed 
> authentication with Shiro?  All the examples I saw did more than that...e.g. 
> Stormpath, etc.
> 
> -Dave
> 
> On Mon, Jun 1, 2015 at 2:37 AM, scSynergy <[email protected]> wrote:
> Shiro starts to shine when the features you need are not provided by the
> other authentication and authorization frameworks, e. g. NoSQL support or
> your users and roles are in different relational databases or one
> authentication framework to serve web and non-web applications
> simultaneously. These use cases are fairly easy to write up and integrate
> yourself with Shiro whereas container authentication or Spring Security
> pretty much block you from any use case but the ones provided - and slight
> variations thereof.
> 
> 
> 
> --
> View this message in context: 
> http://shiro-user.582556.n2.nabble.com/Simple-instructions-on-Shiro-with-GWT-application-tp7580560p7580565.html
> Sent from the Shiro User mailing list archive at Nabble.com.
> 

Reply via email to