SharePoint Integration

This topic introduces the authentication and authorization configuration involved when integrating K2 with SharePoint, especially concerning Claims configuration. There are four options when integrating K2 and SharePoint depends on the version of SharePoint being used.

Depending on your environment, the K2 for SharePoint registration automatically configures Claims or you will have to manually do it. The following table describes these circumstances.

SharePoint Version K2 Integration Requirements
SharePoint 2013/2016 on-premesis
  • K2 integration requires the K2 for SharePoint App
  • Claims is configured automatically if using AD or AAD
  • If not using AD or AAD, Claims configuration is manual
SharePoint Online
  • K2 integration requires the K2 for SharePoint App
  • Only supports AAD
  • Integration with K2

K2 can integrate with the following SharePoint servers:

SharePoint 2013/2016 on-premesis

Integrating K2 with SharePoint 2013 (and SharePoint 2016) requires you to deploy the K2 for SharePoint app to the SharePoint app catalog. This happens during installation when you choose to integrate with SharePoint. All Claims authentication configuration is done automatically during installation for you if your identity store is AD or AAD. If you are authenticating users with a different identity store (e.g. a SQL or a LDAP compatible identity store), you need to configure claims manually to trust the same Identity Providers (IdP) that are trusted in SharePoint.

For more information see the following topics:

SharePoint Online

Integrating K2 with SharePoint Online requires AAD authentication. The K2 Cloud for SharePoint app is also required and is deployed to the app catalog by the operations team. All Claims authentication is configured during installation.

For more information see the topics:

Further Reading