Your feedback is important to us! Email us how we can improve these documents.
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:
- Architecture is important, above all else.
- 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.