Sitecore uses ASP.NET membership for user authentication. If we want to leverage authentication through other mechanisms, there is a lot of custom development comes into picture.
The latest release introduces support for OWIN authentication middleware, which can enable users to log in via standard Microsoft OWIN authentication providers. This can now allow users to log into Sitecore using Azure Active Directory, ADFS, Microsoft, Google, various social media platforms such as Twitter, Facebook, Instagram, or any other third party platforms that support OAuth.
Current OWIN middlewares available include:
- OpenId Connect (AzureAD, identity server)
- Microsoft Account
- Google
- Facebook
- Twitter
- WsFederation
- OAuth
- SAML
Logins can be either Virtual Users or Persisted Users in the membership database. This means that the authentication can be used to both log into the Sitecore CMS as well as for the front-end website (allowing one to identify and collect rich data about your users whilst making it easier for them to use Single Sign On.)
The latest release introduces support for OWIN authentication middleware, which can enable users to log in via standard Microsoft OWIN authentication providers. This can now allow users to log into Sitecore using Azure Active Directory, ADFS, Microsoft, Google, various social media platforms such as Twitter, Facebook, Instagram, or any other third party platforms that support OAuth.
Current OWIN middlewares available include:
- OpenId Connect (AzureAD, identity server)
- Microsoft Account
- WsFederation
- OAuth
- SAML
Logins can be either Virtual Users or Persisted Users in the membership database. This means that the authentication can be used to both log into the Sitecore CMS as well as for the front-end website (allowing one to identify and collect rich data about your users whilst making it easier for them to use Single Sign On.)
No comments:
Post a Comment