Authentication and web services


With Sitefinity CMS you can authenticate services, internal or external, when they need to request resources from Sitefinity CMS. With the Default authentication protocol, you can generate an Access Key that is stored and used to authenticate the requests, while with the OpenID protocol, you can generate access tokens to request access to services.

You can also setup an integration with OAuth2.0 if you need to integrate a small number of applications. For larger or more advanced integrations, it's best to integrate Sitefinity CMS with external identity providers.

Integration with the Default protocol

For Sitefinity CMS projects that use the Default authentication protocol, administrators can generate access key that can be used to authenticate requests. For more information, see Generate access key.

Integration with the OpenID protocol

For Sitefinity CMS projects that use the OpenID authentication protocol, you can use access tokens in HTTP requests to access protected resources such as Sitefinity Web API. For more information, see Request access token for calling web services.

OAuth2.0 integration

The OAuth 2.0 authorization framework enables a third-party application to obtain limited access to an HTTP service, either on behalf of a resource owner by orchestrating an approval interaction between the resource owner and the HTTP service, or by allowing the third-party application to obtain access on its own behalf. For more information, see Configure Oauth2.0Configure Oauth 2.0

Want to learn more?

Sign up for our free beginner training. Boost your credentials through advanced courses and certification.
Register for Sitefinity training and certification.

Was this article helpful?