Member since
01-17-2022
150
Posts
3
Kudos Received
2
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
160 | 09-23-2025 01:31 PM | |
601 | 07-02-2025 08:43 AM |
09-23-2025
01:31 PM
@SLT_Clou You need to create the local user using the command mentioned before. If hdfs user was created for hue as an admin, you can use it to access Hue UI with local authentication. If not, create a new superuser and then login with that to Hue.
... View more
09-22-2025
09:33 PM
1 Kudo
@SLT_Clou From UI we do not have a way to create a local superuser; you will need to do it from the CLI following the steps below: Connect to any of your Hue servers. Run the below commands to create your superuser: export HUE_CONF_DIR="/var/run/cloudera-scm-agent/process/`ls -lrt /var/run/cloudera-scm-agent/process | awk '{print $9}' | egrep -e '[[:digit:]]{1,3}\-hue\-HUE_SERVER' | tail -1`" export HUE_IGNORE_PASSWORD_SCRIPT_ERRORS=1 export HUE_DATABASE_PASSWORD=hue (change this for your Hue backend DB password) Then run the create superuser command: /opt/cloudera/parcels/CDH/lib/hue/build/env/bin/hue createsuperuser --username admin To access Hue using the new superuser, you need to apply a change in the Hue configuration: Access CM >> Hue >> Configuration Look for Authentication Backend Select the option "desktop.auth.backend.LdapBackend,desktop.auth.backend.AllowFirstUserDjangoBackend" Restart Hue service. After applying that change, when you access the Hue UI login page, you will see a drop-down box in which you can select between LDAP and Local authentication, use local, and then log in with the new superuser. Hope the above steps are clear and you can fix your concern. If you have any questions, let me know.
... View more
07-02-2025
08:43 AM
Hi @AdrianMSA The ERROR message you mentioned in the description [1] looks to be very similar to a known issue we have CDPD-43261, which happens when the authentication to Hue is through Knox, but Hue does not have an LB configured. Can you please confirm if you have a Hue LB in front of Hue? If not, can you please install it using CM? After you add the LB, you need to access Clusters > Hue service > Configurations and search for the Knox Proxy Hosts and add the Hue LB by clicking +. TypeError: Object of type WSGIRequest is not JSON serializable
... View more
04-08-2025
10:25 AM
This looks to be due to a known issue we have in Kudu "KUDU-2679" which is unresolved, the best option available is to increase the length of time during which the auth tokens are valid. There is a property for this, and I recommend increasing its value from the default of 7 days up to 90 days (which you can later reduce to the expected timeframe of these jobs running if needed). You will also need to unlock experimental properties if you have not already. CM > Kudu > Configuration > Kudu Master Advanced Configuration Snippet (Safety Valve) for gflagfile: --unlock_experimental_flags --authn_token_validity_seconds=7776000
... View more
02-07-2025
11:50 AM
@zorrofrombrasil Did you get a chance to check the updates from @ggangadharan and @smruti? If so, did the information help to fix the issue? or Do you have any other concerns?
... View more
07-31-2024
03:31 PM
1 Kudo
Hello @caisch Did you add the Hue LB in the Knox Proxy Hosts as mentioned in the documentation? https://docs.cloudera.com/cdp-private-cloud-upgrade/latest/upgrade-hdp/topics/hue-upg-integrate-hue-knox.html#:~:text=If%20you%20have%20deployed%20a%20Hue%20Load%20Balancer%2C%20then%20you%20must%20specify%20the%20Load%20Balancer%20hostname%20in%20the%20Knox%20Proxy%20Hosts%20field%20by%20clicking%20%2B By default, Hue will try to close the Impala query when the user leaves the editor page, this will free all the query resources in Impala, but also make its results inaccessible, however, if you want to ensure that Hue close the Impala queries by adding the following settings to the Hue Service Advanced Configuration Snippet (Safety Valve) for hue_safety_valve.ini configuration property: [impala] close_queries=true query_timeout_s= session_timeout_s= By default query_timeout_s=300 and session_timeout_s=900, you can setup those based on your requirements.
... View more