Sitefinity CMS's legacy authentication methods are no longer considered secure and it is recommended to switch to the Default authentication mechanism. For more information, see Default authentication.
IMPORTANT: This is legacy authentication, consider switching to the Default authentication protocol. For more information, see Default authentication protocol.
The OpenID protocol uses claims authentication, implemented on top of IdentityServer3, certified by OpenID Foundation. It allows implementing single sign-on and access control for modern web applications and APIs. It uses OAuth2 and OpenID Connect protocols. This integration allows easy connection with clients such as mobile, web, SPAs ,and desktop applications. It is also extensible and allows integration in new and existing architectures.
The authentication is designed and implemented as separate Microsoft OWIN / Katana component. It uses standard Microsoft.Owin.Security libraries and standard namespace System.Security. Additionally, there are some extensions to support external provider logins, such as Facebook or LinkedIn.
With the OpenID protocol, you also need to configure your Identity server signing certificate.
The Identity server signing certificate is used to verify the issuer of the authentication token – it is used by Sitefinity CMS Identity provider to sign the identity token . It is also used by Sitefinity CMS Relying party to ensure that the authentication token has been issued by the correct Identity provider.
This certificate is only necessary if you use the OpenID authentication mechanism. For more information, see Authentication.
To configure this certificate:
If you have not configured the certificate, a default certificate for development and testing purposes is used and the System status dashboard widget displays a warning informing you that this is a security risk. For more information, see System status.
You can also check the error logs for information related to the warning displayed in the System status dashboard widget.
NOTE: The certificate must have a private key and the application pool user that runs Sitefinity CMS identity provider must have rights to access it to use it for signing.
As of Sitefinity CMS 14.0, forms-based authentication is no longer supported. If your website uses forms-based authentication and you upgrade your project to Sitefinity CMS 14.x or above, claims-based authentication is not applied automatically. To configure your site to use claims-based authentication, perform the following:
Sign up for our free beginner training. Boost your credentials through advanced courses and certification. Register for Sitefinity training and certification.
To submit feedback, please update your cookie settings and allow the usage of Functional cookies.
Your feedback about this content is important