Error 404 in HUE when configuring it via Knox

[waloz27]

Hi team.

I've been trying to configure Hue with Knox on a Kerberized cluster for quite some time, but I haven't been able to get it working; it generates a 404 error. I configured Knox Advanced admin-topology with the following:

And in Hue Backend: desktop.auth.backend.KnoxSpnegoDjangoBackend.

I'm using Knox's built-in LDAP.

Below is the Knox log.

25/12/02 18:38:41 ||dd3e2a9e-a815-4a09-acf3-7359e0c8a70d|audit|192.168.1.8|HUE||||access|uri|/gateway/default/hue/|unavailable|Request method: GET
25/12/02 18:38:41 ||dd3e2a9e-a815-4a09-acf3-7359e0c8a70d|audit|192.168.1.8|HUE|admin|||authentication|uri|/gateway/default/hue/|success|
25/12/02 18:38:41 ||dd3e2a9e-a815-4a09-acf3-7359e0c8a70d|audit|192.168.1.8|HUE|admin|||authentication|uri|/gateway/default/hue/|success|Groups: []
25/12/02 18:38:41 ||dd3e2a9e-a815-4a09-acf3-7359e0c8a70d|audit|192.168.1.8|HUE|admin|||identity-mapping|principal|admin|success|Groups: [wheel, ollama, admin]
25/12/02 18:38:41 ||dd3e2a9e-a815-4a09-acf3-7359e0c8a70d|audit|192.168.1.8|HUE|admin|||dispatch|uri|http://master01.ambari.local:8888/?doAs=admin|unavailable|Request method: GET
25/12/02 18:38:41 ||dd3e2a9e-a815-4a09-acf3-7359e0c8a70d|audit|192.168.1.8|HUE|admin|||dispatch|uri|http://master01.ambari.local:8888/?doAs=admin|success|Response status: 302
25/12/02 18:38:41 ||dd3e2a9e-a815-4a09-acf3-7359e0c8a70d|audit|192.168.1.8|HUE|admin|||access|uri|/gateway/default/hue/|success|Response status: 302
25/12/02 18:38:42 ||834bde8c-32d8-49ee-a3c7-a7101f0ee18c|audit|192.168.1.8|KNOX||||access|uri|/gateway/default/hue/hue/accounts/login?next=/%253FdoAs%253Dadmin|unavailable|Request method: GET
25/12/02 18:38:42 ||834bde8c-32d8-49ee-a3c7-a7101f0ee18c|audit|192.168.1.8|KNOX|admin|||authentication|uri|/gateway/default/hue/hue/accounts/login?next=/%253FdoAs%253Dadmin|success|
25/12/02 18:38:42 ||834bde8c-32d8-49ee-a3c7-a7101f0ee18c|audit|192.168.1.8|KNOX|admin|||authentication|uri|/gateway/default/hue/hue/accounts/login?next=/%253FdoAs%253Dadmin|success|Groups: []
25/12/02 18:38:42 ||834bde8c-32d8-49ee-a3c7-a7101f0ee18c|audit|192.168.1.8|KNOX|admin|||identity-mapping|principal|admin|success|Groups: [wheel, ollama, admin]
25/12/02 18:38:42 ||834bde8c-32d8-49ee-a3c7-a7101f0ee18c|audit|192.168.1.8|KNOX|admin|||access|uri|/gateway/default/hue/hue/accounts/login?next=/%253FdoAs%253Dadmin|success|Response status: 404

ODP: 1.2.4.0-115
Ambari: 2.7.11
Rocky Linux release 8.10

Thank you for your valuable help.

[lucasbak]

Hi @waloz27,

can you make sure than in the rendered topoly file (xml in /etc/knox/conf) HUE is correctly appearing ?

Regards,

Clemlab Team

[waloz27]

Hi @lucasbak

I see it configured in the admin.xml file at /etc/knox/conf/topologies

As shown below

I'm trying it on a Kerberized cluster and on one without Kerberos, and it gives the same error.

What do you think it could be? Thanks for the help.

[lucasbak]

I think that Knox does simply not deploy the new topology for whatever reason.
We are using knox + hue using ODP 1.2.40 which means that there is no issues on the stack level for your problem.

Check the logs of knox gateway to see why it does not re-deploy the topology using hue.
try to create a new topology, because admin is generally reserver for knox ui configurations

Clemlab team

[waloz27]

Hi @lucasbak

Initially, I tried configuring the services in the Advanced Topology settings, but the changes weren't saved. When I restart the Knox service, the default.xml topology file is always overwritten and ends up with the same configuration as admin.xml. In other words, the Advanced Topology settings aren't being saved to any XML file.

This appears to be a bug in the Knox stack.