Shibboleth 和 CAS 之间的区别？
请解释一下 Shibboleth 和 CAS 之间有什么区别？
Please explain what the differences are between Shibboleth and CAS?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
请解释一下 Shibboleth 和 CAS 之间有什么区别？
Please explain what the differences are between Shibboleth and CAS?
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
接受 或继续使用网站，即表示您同意使用 Cookies 和您的相关数据。
发布评论
评论（3）
第一个 (Shibboleth) 是服务器，第二个 (CAS) 是协议。将中央身份验证服务 (CAS) 与 安全断言标记语言 (SAML)，这是 Shibboleth 使用的协议。两者都可用于实现集中式单点登录 (SSO)。
The first (Shibboleth) is a server and the second (CAS) a protocol. It makes more sense to compare Central Authentication Service (CAS) with Security Assertion Markup Language (SAML), which is the protocol used by Shibboleth. Both can be used to implement a centralized Single Sign-On (SSO).
许多人将 CAS 和 Shibboleth 结合使用。将 CAS 视为（通常存储在 LDAP 中的用户的）身份验证和（请求的 Web 服务的）授权引擎。 Shibboleth 实际上是两个组件，请求属性的 SP（服务提供商）和广播属性的 IDP（身份提供商），它是一个联合引擎，一旦用户拥有属性，属性（可能也存储在同一个 LDAP 中）就可用。已通过身份验证并授权服务。
虽然两者都可用于提供 SSO，但 CAS 最擅长管理会话状态（以及可能的持久性），而 Shibboleth 最擅长解析和呈现服务提供商请求的属性。我已经实现了 CAS 和 Shibboleth，并在 上找到了文档Shibboleth 和 Jasig(CAS)维基百科有很大用处。
Many people use CAS and Shibboleth in conjunction with each other. Look at CAS as an authentication (of the user usually stored in LDAP) and authorization (of the requesting web service) engine. Shibboleth, which is actually two components, the SP (Service Provider) which requests attributes and the IDP (Identity Provider) which broadcasts attributes, is a federating engine which makes the attributes (possibly also stored in the same LDAP) available once the user has been authenticated and the service authorized.
While both can be used to provide SSO, CAS is best at managing the session state (and possible persistence) while Shibboleth is best at parsing and presenting attributes requested by service providers. I've implemented both CAS and Shibboleth and found the documentation at both the Shibboleth and the Jasig(CAS) wikis to be of great use.
CAS 是一种身份验证提供程序，最适合通过一次登录对许多服务/应用程序进行单点登录。然而，CAS 在向服务释放附加属性方面有其局限性。这就是 Shib 的最大优势，因为它使管理员能够为不同的服务配置一组独特的属性。
BMW先生，您是如何整合CAS和Shib的？看起来有几种方法可以做到这一点。 CAS 是我们的主要认证提供商，我们对此进行了大量投资。我们最近安装了 Shib，想知道集成两者的最佳方法是什么。任何见解将不胜感激。
CAS is an authentication provider which is best used for Single-Sign-On to many services/applications with one logon. However, CAS has its limitation of releasing additional attributes to service. That's where Shib has its most advantage as it provides administrators the ability to configure a unique set of attributes to different services.
Mr.BMW, how did you integrate CAS and Shib? It looks like there are several ways of doing it. CAS is our primary authentication provider and we have heavy investments in there. We recently got Shib installed and wonder what is the best way to integrate both. Any insight would be appreciated.