[jira] [Commented] (DIRKRB-665) Hive ODBC kerberos SASL(-1): generic failure _ GSSAPI Error

2017-11-06 Thread Venkat Atmuri (JIRA) 

[ 
https://issues.apache.org/jira/browse/DIRKRB-665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16240287#comment-16240287
 ] 

Venkat Atmuri commented on DIRKRB-665:
--

Yes,I'm using MIT KDC with Centrify.

It was problem with Principal and Host FQDN.


Thank you to everyone.

> Hive ODBC  kerberos   SASL(-1): generic failure _ GSSAPI Error
> --
>
> Key: DIRKRB-665
> URL: https://issues.apache.org/jira/browse/DIRKRB-665
> Project: Directory Kerberos
>  Issue Type: Bug
>Reporter: Venkat Atmuri
> Attachments: KDC ODBC Driver Cloudera.PNG, kdc ticket cloudera.PNG
>
>
> Hi,
> We have Cloudera Kerborised Cluster.
> I'm able to use the Impala ODBC Driver on a Windows Machine, authenticate 
> with a USERNAME  and PASSWORD using SASL.
> !attachment-name.jpg|thumbnail!
>  
> When I try to connect to the Hive ODBC authenticate with Kerberos. I get the 
> following error message:
>  
> FAILED!
> [Microsoft][Hardy] (34) Error from server: SASL(-1): generic failure: GSSAPI 
> Error: Unspecified GSS failure. Minor code may provide more information 
> (Server not found in Kerberos database).
>  
> Tried:
> KRB5_CONFIG = C:\Program Files\MIT\Kerberos5\krb5.ini
> KRB5CCNAME =C:\temp\krb5cache
>  
> C:\Program Files\MIT\Kerberos5\venkata.keytab
> C:\Program Files\MIT\Kerberos5>krb5.ini(config)
> [libdefaults]
> default_realm = MYKDC.YSTAT.COM
> dns_lookup_kdc = false
> dns_lookup_realm = false
> ticket_lifetime = 86400
> renew_lifetime = 604800
> forwardable = true
> default_tgs_enctypes = aes256-cts aes128-cts
> default_tkt_enctypes = aes256-cts aes128-cts
> permitted_enctypes = aes256-cts aes128-cts
> udp_preference_limit = 1
> kdc_timeout = 3000
> max_life = 1d 
> max_renewable_life = 7d
> kdc_tcp_ports = 88
> ticket_lifetime = 24h
> renew_lifetime = 7d
> forwardable = true
> [realms]
> MYKDC.YSTAT.COM= {
> kdc = dc1.MYKDC.YSTAT.COM
> admin_server = dc1.MYKDC.YSTAT.COM
> max_renewable_life = 7d 0h 0m 0s
> default_principal_flags = +renewable
> }
>  
>  
> Tried by using different drivers(Simba, Microsoft, Cloudera)Created new users 
> and new keytabs.
>  
>  
> Any ideas on this error?
>  
> Thanks.
>  
>  



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (DIRKRB-665) Hive ODBC kerberos SASL(-1): generic failure _ GSSAPI Error

2017-11-01 Thread Kai Zheng (JIRA) 

[ 
https://issues.apache.org/jira/browse/DIRKRB-665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16233787#comment-16233787
 ] 

Kai Zheng commented on DIRKRB-665:
--

Looks like the service principal sent by the client side failed to match, so 
please double check and make sure it's the right one in the KDC database.

> Hive ODBC  kerberos   SASL(-1): generic failure _ GSSAPI Error
> --
>
> Key: DIRKRB-665
> URL: https://issues.apache.org/jira/browse/DIRKRB-665
> Project: Directory Kerberos
>  Issue Type: Bug
>Reporter: Venkat Atmuri
>Priority: Major
> Attachments: KDC ODBC Driver Cloudera.PNG, kdc ticket cloudera.PNG
>
>
> Hi,
> We have Cloudera Kerborised Cluster.
> I'm able to use the Impala ODBC Driver on a Windows Machine, authenticate 
> with a USERNAME  and PASSWORD using SASL.
> !attachment-name.jpg|thumbnail!
>  
> When I try to connect to the Hive ODBC authenticate with Kerberos. I get the 
> following error message:
>  
> FAILED!
> [Microsoft][Hardy] (34) Error from server: SASL(-1): generic failure: GSSAPI 
> Error: Unspecified GSS failure. Minor code may provide more information 
> (Server not found in Kerberos database).
>  
> Tried:
> KRB5_CONFIG = C:\Program Files\MIT\Kerberos5\krb5.ini
> KRB5CCNAME =C:\temp\krb5cache
>  
> C:\Program Files\MIT\Kerberos5\venkata.keytab
> C:\Program Files\MIT\Kerberos5>krb5.ini(config)
> [libdefaults]
> default_realm = MYKDC.YSTAT.COM
> dns_lookup_kdc = false
> dns_lookup_realm = false
> ticket_lifetime = 86400
> renew_lifetime = 604800
> forwardable = true
> default_tgs_enctypes = aes256-cts aes128-cts
> default_tkt_enctypes = aes256-cts aes128-cts
> permitted_enctypes = aes256-cts aes128-cts
> udp_preference_limit = 1
> kdc_timeout = 3000
> max_life = 1d 
> max_renewable_life = 7d
> kdc_tcp_ports = 88
> ticket_lifetime = 24h
> renew_lifetime = 7d
> forwardable = true
> [realms]
> MYKDC.YSTAT.COM= {
> kdc = dc1.MYKDC.YSTAT.COM
> admin_server = dc1.MYKDC.YSTAT.COM
> max_renewable_life = 7d 0h 0m 0s
> default_principal_flags = +renewable
> }
>  
>  
> Tried by using different drivers(Simba, Microsoft, Cloudera)Created new users 
> and new keytabs.
>  
>  
> Any ideas on this error?
>  
> Thanks.
>  
>  



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (DIRKRB-665) Hive ODBC kerberos SASL(-1): generic failure _ GSSAPI Error

2017-10-31 Thread Jiajia Li (JIRA) 

[ 
https://issues.apache.org/jira/browse/DIRKRB-665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16233581#comment-16233581
 ] 

Jiajia Li commented on DIRKRB-665:
--

I think your are using the MIT Kerberos.
The reason for the error is "Server not found in Kerberos database", you should 
add the service principal in Kerberos database.

> Hive ODBC  kerberos   SASL(-1): generic failure _ GSSAPI Error
> --
>
> Key: DIRKRB-665
> URL: https://issues.apache.org/jira/browse/DIRKRB-665
> Project: Directory Kerberos
>  Issue Type: Bug
>Reporter: Venkat Atmuri
>Priority: Major
> Attachments: KDC ODBC Driver Cloudera.PNG, kdc ticket cloudera.PNG
>
>
> Hi,
> We have Cloudera Kerborised Cluster.
> I'm able to use the Impala ODBC Driver on a Windows Machine, authenticate 
> with a USERNAME  and PASSWORD using SASL.
> !attachment-name.jpg|thumbnail!
>  
> When I try to connect to the Hive ODBC authenticate with Kerberos. I get the 
> following error message:
>  
> FAILED!
> [Microsoft][Hardy] (34) Error from server: SASL(-1): generic failure: GSSAPI 
> Error: Unspecified GSS failure. Minor code may provide more information 
> (Server not found in Kerberos database).
>  
> Tried:
> KRB5_CONFIG = C:\Program Files\MIT\Kerberos5\krb5.ini
> KRB5CCNAME =C:\temp\krb5cache
>  
> C:\Program Files\MIT\Kerberos5\venkata.keytab
> C:\Program Files\MIT\Kerberos5>krb5.ini(config)
> [libdefaults]
> default_realm = MYKDC.YSTAT.COM
> dns_lookup_kdc = false
> dns_lookup_realm = false
> ticket_lifetime = 86400
> renew_lifetime = 604800
> forwardable = true
> default_tgs_enctypes = aes256-cts aes128-cts
> default_tkt_enctypes = aes256-cts aes128-cts
> permitted_enctypes = aes256-cts aes128-cts
> udp_preference_limit = 1
> kdc_timeout = 3000
> max_life = 1d 
> max_renewable_life = 7d
> kdc_tcp_ports = 88
> ticket_lifetime = 24h
> renew_lifetime = 7d
> forwardable = true
> [realms]
> MYKDC.YSTAT.COM= {
> kdc = dc1.MYKDC.YSTAT.COM
> admin_server = dc1.MYKDC.YSTAT.COM
> max_renewable_life = 7d 0h 0m 0s
> default_principal_flags = +renewable
> }
>  
>  
> Tried by using different drivers(Simba, Microsoft, Cloudera)Created new users 
> and new keytabs.
>  
>  
> Any ideas on this error?
>  
> Thanks.
>  
>  



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (DIRKRB-665) Hive ODBC kerberos SASL(-1): generic failure _ GSSAPI Error

2017-10-31 Thread Colm O hEigeartaigh (JIRA) 

[ 
https://issues.apache.org/jira/browse/DIRKRB-665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16226519#comment-16226519
 ] 

Colm O hEigeartaigh commented on DIRKRB-665:


Are you using Apache Kerby as the KDC? It's not clear from the JIRA 
description...

> Hive ODBC  kerberos   SASL(-1): generic failure _ GSSAPI Error
> --
>
> Key: DIRKRB-665
> URL: https://issues.apache.org/jira/browse/DIRKRB-665
> Project: Directory Kerberos
>  Issue Type: Bug
>Reporter: Venkat Atmuri
> Attachments: KDC ODBC Driver Cloudera.PNG, kdc ticket cloudera.PNG
>
>
> Hi,
> We have Cloudera Kerborised Cluster.
> I'm able to use the Impala ODBC Driver on a Windows Machine, authenticate 
> with a USERNAME  and PASSWORD using SASL.
> !attachment-name.jpg|thumbnail!
>  
> When I try to connect to the Hive ODBC authenticate with Kerberos. I get the 
> following error message:
>  
> FAILED!
> [Microsoft][Hardy] (34) Error from server: SASL(-1): generic failure: GSSAPI 
> Error: Unspecified GSS failure. Minor code may provide more information 
> (Server not found in Kerberos database).
>  
> Tried:
> KRB5_CONFIG = C:\Program Files\MIT\Kerberos5\krb5.ini
> KRB5CCNAME =C:\temp\krb5cache
>  
> C:\Program Files\MIT\Kerberos5\venkata.keytab
> C:\Program Files\MIT\Kerberos5>krb5.ini(config)
> [libdefaults]
> default_realm = MYKDC.YSTAT.COM
> dns_lookup_kdc = false
> dns_lookup_realm = false
> ticket_lifetime = 86400
> renew_lifetime = 604800
> forwardable = true
> default_tgs_enctypes = aes256-cts aes128-cts
> default_tkt_enctypes = aes256-cts aes128-cts
> permitted_enctypes = aes256-cts aes128-cts
> udp_preference_limit = 1
> kdc_timeout = 3000
> max_life = 1d 
> max_renewable_life = 7d
> kdc_tcp_ports = 88
> ticket_lifetime = 24h
> renew_lifetime = 7d
> forwardable = true
> [realms]
> MYKDC.YSTAT.COM= {
> kdc = dc1.MYKDC.YSTAT.COM
> admin_server = dc1.MYKDC.YSTAT.COM
> max_renewable_life = 7d 0h 0m 0s
> default_principal_flags = +renewable
> }
>  
>  
> Tried by using different drivers(Simba, Microsoft, Cloudera)Created new users 
> and new keytabs.
>  
>  
> Any ideas on this error?
>  
> Thanks.
>  
>  



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)