春季安全VS阿帕奇四郎 [英] Spring security vs Apache Shiro

查看:135
本文介绍了春季安全VS阿帕奇四郎的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我已经研究到目前为止大多数人都在说阿帕奇四郎是易于使用和易于使用CAS(为SSO等)的集成。只是问,如果任何人有使用他们与使用哪一个经验,为什么一个是比其他更好吗?

What I have researched so far most people are saying Apache Shiro is easy to use and easy to integrate with CAS (for SSO etc). Just to ask if anyone has experience using both of them and which one to use and why one is better than other?

推荐答案

我最近不得不同时评估四郎和春季安全。我们去使用Spring Security(其实我们扩展Spring Security的使用许可四郎字符串以更好的方式 - 与annoations实例变量)

I have recently had to evaluate both shiro and spring security. We went with spring security (in fact we extended spring security to use the shiro permission strings in a better way - with instance variables on annoations).

春季安全

  • under active development.
  • has much more community support.
  • Spring security has extensions providing support for both Oauth and kerberos and SAML.

四郎


  • 不支持SAML或的Oauth。

  • 只字不提支持之前和安全政策之后。

  • 积极发展似乎有限,仍网站
    包含错误的信息

  • Does not support saml or Oauth.
  • Makes no mention of supporting before and after security policies.
  • Active development seems limited, the website still contains erroneous information.

这篇关于春季安全VS阿帕奇四郎的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆