问题描述
我知道IdentityServer3提供了实现OAuth 2.0，OpenId Conect等的整个堆栈.我不知道是否应该使用IdentityServer3.因为我有自己的登录服务器，该服务器使用已可用的成员资格提供程序对用户进行身份验证.我可以将我已经可用的登录机制与IdentityServer3集成，并实现OAuth 2.0吗?
I know that IdentityServer3 provides the whole stack of implementing OAuth 2.0, OpenId Conect etc. I don't know if I should use IdentityServer3. Because I have my own login server which authenticates the user using a membership provider which is already available. Can I integrate my already available login mechanism with IdentityServer3 and implement OAuth 2.0?
任何建议将不胜感激.
Any suggestion will be highly appreciated.
推荐答案
将成员身份部分移动到Identityserver很容易.如果您希望保持整个登录体验"不变，但是将idsrv用于协议支持-则需要做更多的工作.
Moving the membership part to identityserver is easy. If you want to keep the whole "login experience" just the same but use idsrv for protocol support - this is more work.
您可以将登录应用程序移至idsrv并使用部分登录概念.这需要您现有的登录页面与idsrv OWIN扩展方法进行交互.
You can move your login app into idsrv and use the partial login concept. This requires your existing login page to interact with the idsrv OWIN extension methods.
另一种选择是将登录应用程序封装为Katana身份验证中间件，并将其作为外部提供程序插入idsrv.
Another option is to encapsulate your login app as Katana authentication middleware and plug it into idsrv as an external provider.
这篇关于使用IdentityServer3和现有的登录服务器和成员资格提供程序来实现OAuth 2.0和OpenId Connect提供程序的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！