Driver Details | Formatted as .csv, .avro |
Type of Support | Read & Write |
Validated On | 2.5.0 |




Kerberos support for reading and writing to HDFS is available via the Input Data, Output Data, Connect In-DB, and Data Stream In tools. There are 3 Kerberos options in the HDFS Connection window. The option you choose depends on how your IT admin configured the HDFS server:
None: No authentication is used.
KerberosMIT: Alteryx uses the default MIT ticket to authenticate with the server. You must first acquire a valid ticket using the MIT Kerberos Ticket Manager. In the output tool, the username must match the service principal name used to create the ticket.
KerberosSSPI: Alteryx uses Windows Kerberos keys for authentication, which are obtained when logging in to Windows with your Windows credentials. The User Name and Password fields are therefore not available.