ASP.NET Single Sign On CrossDomain with OneLogin and DotNetOpenAuth

I am working on a project requiring a single sign for cross-domain (non-sub-domain) authentication for 2 websites.

I searched for what others said here and on the Internet and tried to use DotNetOpenAuth, but I canโ€™t interpret it, and the documentation doesnโ€™t help much. So I turned to OneLogin , which seems to provide what I want, but again, the documentation is missing. I think I need to use both of them, but I cannot connect the pieces of the puzzle.

I'm getting closer to implementing my own SSO solution based on Unified Security for Web Applications , but you want to avoid this as it will take much longer and be more error prone than using an existing solution.

So now for some questions for all gurus:

  • Can you shed some light on how to use DotNetOpenAuth to authenticate users in OneLogin?
  • Where can I get some more examples for OneLogin?
  • As for DotNetOpenAuth for those who tried the VS2010 project template, did it make RelyingPartyLogic.dll compiled or missing? Where can i get this?

Thank you for your help!

+5
source share
1 answer

DotNetOpenAuth OpenID, OAuth InfoCard. OneLogin SAML -sso SAML. .

OneLogin.NET https://onelogin.zendesk.com/entries/20186386-introduction-to-onelogin-s-saml-toolkits

DotNetOpenAuth , , OpenID 2- ; , , SAML ( ). (, ), ( ).

OpenID SAML, , . , : https://onelogin.zendesk.com/entries/270738-openid-or-saml-for-enterprise-sso

+4

All Articles