About: Integrated Windows Authentication is a research topic. Over the lifetime, 2 publications have been published within this topic receiving 3 citations.
TL;DR: This paper reviews how Kerberos is used with the SAS Business Analytics Framework, explores the considerations and constraints when using Kerbero, and summarizes solutions for some common issues.
Abstract: Kerberos is a network authentication protocol designed to provide strong authentication for client/server applications by using secret-key cryptography. With the release of SAS® 9.4, there are three ways Kerberos can be used with the SAS® Business Analytics Framework. Kerberos provides Integrated Windows authentication from a range of clients to a range of servers. This paper reviews how Kerberos is used with the SAS Business Analytics Framework. It explores the considerations and constraints when using Kerberos and summarizes solutions for some common issues. Once we provide a better understanding of the Kerberos authentication protocol, we examine how the SAS Business Analytics Framework can leverage Kerberos authentication. We look at the different parts of the SAS Business Analytics Framework and see how they fit into the Kerberos authentication protocol. This continues into reviewing how the support of Kerberos authentication has changed over the SAS releases from SAS® 9.2 to SAS 9.4. When examining the SAS Business Analytic Framework, we consider the server tier, middle tier, and client tier. Of specific interest within this section of the paper are those SAS client applications that do not support the use of the Kerberos authentication protocol. In addition, we review some of the constraints for using Kerberos authentication. We illustrate how the use of Kerberos is tied into the domain trust structure and show some of the prerequisites of using Kerberos. Of these prerequisites, we identify the clear importance of the Service Principal Name and how this is central to the Kerberos authentication protocol. Finally, we review some of the common issues that arise when using Kerberos and identify solutions to those error messages. Although troubleshooting Kerberos authentication issues is beyond the scope of this paper, it should be made easier by the understanding of the authentication process we present. Understanding the steps in the authentication process is the first and biggest step in being able to troubleshoot issues.
TL;DR: The Logical Model and the Physical Models, used by Analysis Services, to provide HTTP/HTTPS access thought the IIS Web Server, will be analyzed, and the steps required to setting it up will be explained.
Abstract: Analysis Services disposes three Access Mechanisms: Direct Access, HTTP/HTTPS Access and XMLA Access. From among these mechanisms, the Direct Access is that one that guarantees the lowest response time and the strongest security, characteristics that turn it the mechanism of preferential use. But this mechanism can be used only in intradomain accesses, by imposition of the Authentication Mechanism that it uses, the Integrated Windows Authentication. When the Client and the Analysis Services doesn’t share the same domain, or when the access must be made by Internet, can be used the HTTP/HTTPS Access Mechanism. However, the use of this mechanism is not trivial, presenting some peculiarities; a consequence of Analysis Services doesn’t to support, by him self, HTTP/HTTPS Accesses. In fact, HTTP/HTTPS Access to Analysis Services is provided by the IIS Web Server. In this paper, the Logical Model and the Physical Models, used by Analysis Services, to provide HTTP/HTTPS access thought the IIS Web Server, will be analyzed, and will be explained the steps required to setting it up. The Mechanisms of Security and Access Control, used by Analysis Services, will be analyzed too, being covered both Users Authentication and Security Roles Definition.