Windows Identity Foundation-IdentityProvider 发起的 SSO

发布于 2024-12-29 07:48:56 字数 307 浏览 6 评论 0原文

感谢您的阅读。我正在尝试在我的网站 (Site1) 和我们关联的另一个网站 (Site2) 之间执行 SSO。我想使用 WIF 和 STS。我的网站已连接到 SQL Server 数据库,并且我针对该数据库进行身份验证。通过身份验证后,我想在主页上显示一个链接/图标,链接到其他站点(site2)并提供其他站点(site2)所需的声明。从我在网上看到的情况来看,大多数情况是在 site2 上请求资源时,系统重定向到 STS 站点,并且在 STS 成功登录后,声明将呈现给 site2 并为用户提供访问权限。如何实现 IDP 发起的 SSO?单击登录后的链接时,我想对 site2 页面进行身份验证。

Thanks for reading. I am trying to perform SSO between my website(Site1) and another site(Site2) that we have association with. I'd like to use WIF and STS. My website is already connected to a SQL server database and i authenticate against that database. Once I'm authenticated, I'd like to show a link/icon on my main page that links to the other site(site2) and provides the claims that the other site(site2) needs. From what I've seen online its mostly the case that on requesting a resource on site2, the system redirects to STS site and on successful login at the STS the claims are presented to the site2 and user is provided access. How can i achieve IDP initiated SSO? On clicking a link post login, i'd like to authenticate to site2 page.

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(1

別甾虛僞 2025-01-05 07:48:56

使用基于声明的身份验证(使用 WIF 和 ASP.NET)的此方案的最简单实现是让 Site1 和 Site2 都信任 STS。所以会有 3 个组件。其他答案(以及您的问题)似乎表明 Site1 和 STS 是一个整体,通常不建议这样做。

在此处输入图像描述

序列为:

  1. 用户首次访问 Site1。既然他是
    未经身份验证,他会被重定向到 STS。
  2. STS 对用户进行身份验证并为 Site1 颁发令牌。与用户创建会话。
  3. 浏览器将令牌发回到另一个会话所在的 Site1
    创建的。
  4. 用户单击 Site2 的链接。对于 Site2,用户是
    未经身份验证,因此重定向到 STS
  5. 用户到达 STS。他已经通过身份验证,STS 继续为以下对象颁发第二个令牌
    Site2(可能且经常具有不同的声明)
  6. 浏览器将第二个令牌发回 Site2。会话已创建。

更新:
声明指南的本章讨论 SharePoint 特定设置和配置。
http://msdn.microsoft.com/en-us/library/hh446525。 ASPX

The simplest implementation of this scenario with claims based authentication (with WIF and ASP.NET) is to have Site1 and Site2 both trust an STS. So there would be 3 components. The other answers (and your question) seem to suggest that Site1 and the STS are a single thing, which is not generally recommended.

enter image description here

Sequence would be:

  1. User goes to Site1 for the first time. Since he is
    unauthenticated, he is redirected to the STS.
  2. STS authenticates user and issues a token for Site1. Creates a session with the user.
  3. Browser posts back the token to Site1 where another session is
    created.
  4. User clicks on a link to Site2. For Site2, the user is
    unauthenticated, so redirects to STS
  5. User reaches the STS. He is already authenticated, STS proceeds to issue a second token for
    Site2 (potentially and often with different claims)
  6. Browser posts back 2nd token to Site2. Session is created.

Update:
This chapter of the claims guide talks about SharePoint specific settings and config.
http://msdn.microsoft.com/en-us/library/hh446525.aspx

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文