PRODUCT: K2 Cloud, K2 Five, K2 blackpearl 4.7
These are external resources you can use to learn more about claims:
- How Claims Based Authentication works – YouTube: https://www.youtube.com/watch?v=_DJUvkbcT8E
- Claims-based identity and concepts in SharePoint 2013: https://msdn.microsoft.com/en-us/library/office/ee539091.aspx
- Passive Authentication for ASP.NET with WIF: https://msdn.microsoft.com/en-us/magazine/ff872350.aspx
- Configure an environment for apps for SharePoint (SharePoint 2013): https://technet.microsoft.com/en-us/library/fp161236.aspx
- A Guide to Claims-Based Identity and Access Control (2nd Edition): https://msdn.microsoft.com/en-us/library/ff423674.aspx
In the first article in this series, you got an overview of authentication and authorization as it relates to K2. This document focuses on Claims-Based authentication (CBA) in K2.
Claims-Based Authentication is a consistent approach for applications to get and verify identity information across multiple systems. Whether it's inside an enterprise organization, through a different provider, or on the internet, claims-based authentication can simplify and standardize authentication logic and flow across various systems.
Not every organization needs CBA – some companies may be built entirely on applications that use Integrated Windows Authentication and Kerberos, and many of the benefits inherent in CBA are present in Kerberos. However, as soon as these companies introduce non-Windows apps, they need to federate identity management with a partner or web property, or they need to introduce SharePoint 2013/2016 into their environment, they must start down the CBA path.
Once you start down the CBA path, you must train your internal infrastructure team to be able to understand, configure and support CBA. This requires specialized configuration and specific know-how to troubleshoot CBA-related issues.
Due to the length of this article, the full content cannot be displayed here. Please read the full article in the attachment below