Best Practice - Pentaho, Linux, & MSAD Authentication with Kerberos

Your feedback is important to us!  Email us how we can improve these documents.

Software Version
Pentaho  6.x
Windows Server 2012R2
MS SQL Server 2012
Ubuntu  14.04
Oracle Java 1.8 JRE

Overview

Many enterprises require that all of their connections to different databases be authenticated via a Kerberos ticket. This applies to all JDBC-type connections including both BA and DI Repository connections (hibernate, quartz, and jackrabbit); solution connections, which are configured in the context.xml through the manage datasources in the Pentaho User Console (PUC); and in a job or transformation.

Keep these Pentaho Architecture principles in mind while you are working through this document:

  1. Architecture is important, above all else.
  2. Platforms are always evolving: sometimes you will have to think creatively.

Some of the things discussed here include Windows authentication, Kerberos, Microsoft SQL Server, Linux, kinit, klist, Pentaho BA and DI Server.

 

   -  Best Practice - Pentaho, Linux, & MSAD Authentication with Kerberos

Have more questions? Submit a request

Comments

Powered by Zendesk