Web 应用程序和虚拟目录中的应用程序的单点登录
为了对 Web 应用程序和虚拟目录中的 Web 应用程序启用单点登录，我将两个应用程序中的 machinekey 设置为相同：
<machineKey validationKey="xxx" decryptionKey="yy" validation="SHA1" />
单点登录工作正常，但现有用户无法再登录；他们的密码被拒绝。父应用程序中的机器密钥曾经是这样的：
<machineKey validationKey="xxx,IsolateApps" decryptionKey="yy,IsolateApps" validation="SHA1" />
我尝试了其他方法来使单点登录工作，但只要密钥包含“IsolateApps”，它就不会。我缺少什么？
我应该补充一点，在会员资格提供程序中，passwordFormat 设置为“加密”。因此，我假设密码是使用包含“IsolateApps”的密钥加密的，现在当它尝试验证密码时，它使用的是不带“IsolateApps”的密钥。仍然不确定如何解决这个问题。有没有一种方法可以将密码的加密密钥与用于身份验证 cookie 的加密密钥分开设置？
To enable single sign-on for a web application and a web application in a virtual directory, I set the machinekey in both apps to the same:
<machineKey validationKey="xxx" decryptionKey="yy" validation="SHA1" />
The single sign on works just fine, but existing users can't sign in any more; their passwords are rejected. The machinekey used to be this in the parent application:
<machineKey validationKey="xxx,IsolateApps" decryptionKey="yy,IsolateApps" validation="SHA1" />
I tried other ways to make single sign on work, but it just won't as long as the keys contain "IsolateApps". What am I missing?
I should add that the in the membership provider, passwordFormat is set to "Encrypted". So I assume the password was encrypted using the key that contained "IsolateApps" and now when it tries to validate the password it's using the key without the "IsolateApps". Still not sure how to solve that problem. Is there maybe a way that I can set the encryption keys for the password separately from the one that is used for the authentication cookie?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
在设置单点登录之前，您的现有用户密码将使用不同的密钥进行加密。
设置单点登录时，您可以指定用于 SSO 中涉及的每个网站的密钥。
这与自动生成的密钥不同
，因此您的用户将需要使用新密钥重新加密其密码
Prior to setting up single sign on, your existing users passwords will have been encrypted with a different key
When setting up single sign on, you specify the key to use for each website involved in SSO.
This will be different to the autogenerated key
So your users will need to have their passords rencrypted by the new key