@ishashrestha, please let us know if you have any further queries regarding the details shared above. ... View more

Hi @Joyful  Have you been able to resolve your issue? If so, please mark the appropriate reply as the solution, as it will make it easier for others to find the answer in the future. ... View more

@upadhyayk04 - thanks will upgrade the runtime version. ... View more

Hi @upadhyayk04  Context: I have access to CDP Data Warehouse and can log in to the Hue console via browser using SSO (Single Sign-On). I want to connect to Impala using the impala-shell CLI tool or JDBC driver for querying data. I attempted to ingest data using Python through the Cloudera AI console by creating a new project, but I am still encountering the same access permission issues. What I Have Tried: Successfully listed clusters and warehouses using cdp dw CLI commands. Retrieved the Impala JDBC connection string and endpoint details. Tried to start the virtual warehouse using CLI but faced permission denied (403) errors. Attempted to connect via impala-shell CLI with LDAP username and password, but received HTTP 401 Unauthorized errors. Verified that no LDAP password is available as login is via SSO. Tried to pass password in command line and interactively; none worked. Noted that impala-shell does not support browser-based SSO authentication. Attempted to add users to virtual warehouse using cdp dw add-user but faced permission denied errors. Confirmed that SSO login works fine in Hue and CDP Console but CLI access is blocked due to lack of proper credentials. Issue: CLI tools like impala-shell and cdp dw commands require LDAP credentials or a different authentication method. SSO-based authentication used in the environment is not supported by CLI tools by default. This prevents me from running queries or managing the Data Warehouse via CLI. Thank You, Venkat ... View more

The error means the SSL certificates used by your Cloudera ODBC driver are outdated or expired. To fix it, download the latest cacerts.pem file from a trusted source like Curl's CA bundle or your company’s security team. Replace the old cacerts.pem file in the ODBC driver's configuration directory. Then restart your ODBC connection and test again. ... View more

Hello @RamaClouder  Thank you for reaching out to Cloudera community Could you please confirm if you have tried the same in incognito mode as well? Thank you Kshitij Upadhyay ... View more

Hi @upadhyayk04, thanks for you answer and the link to the documentation you pointed us. But we have read the documentation multiple time but it doesn't help us We need to understand why we get this error. So we still get the error. By mistake I pressed the resolve button, even the problem is not solved. Is there any way to reopen this post ?     ... View more

Kshitij, Wow, that worked like a charm. When I was granting privileges to the database, I was using the following statement for all three of those including the actual password, but that did not work for me. GRANT ALL ON rman.* TO 'rman'@'%' IDENTIFIED BY 'password'; I am not really a DB person, so figured I would get the right solution from someone that is. I was going to say to keep an eye for my next posted issue regarding HDFS, but it looks like after fixing the DB issue and after restarting HDFS, we are all GREEN now!!! ... View more