Issue when activating saml backend with hue 4.10.0 inside a docker container #2618

max-l-f · 2021-08-30T15:53:31Z

max-l-f
Aug 30, 2021

Hello,
I have a hue version 4.8.0 working properly using the official hue docker image and I'm trying to bump the version to 4.10.0 but I've encounterd the following problem:

Describe the bug:
When I activate and configure hue with a saml backend as it was with version 4.8.0 I get the following error:

Traceback (most recent call last):
File "/usr/share/hue/build/env/lib/python3.6/site-packages/django/urls/resolvers.py", line 600, in url_patterns
iter(patterns)
TypeError: 'module' object is not iterable

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
File "./build/env/bin/hue", line 33, in
sys.exit(load_entry_point('desktop', 'console_scripts', 'hue')())
File "/usr/share/hue/desktop/core/src/desktop/manage_entry.py", line 236, in entry
raise e
File "/usr/share/hue/desktop/core/src/desktop/manage_entry.py", line 230, in entry
execute_from_command_line(sys.argv)
File "/usr/share/hue/build/env/lib/python3.6/site-packages/django/core/management/init.py", line 419, in execute_from_command_line
utility.execute()
File "/usr/share/hue/build/env/lib/python3.6/site-packages/django/core/management/init.py", line 413, in execute
self.fetch_command(subcommand).run_from_argv(self.argv)
File "/usr/share/hue/build/env/lib/python3.6/site-packages/django/core/management/base.py", line 354, in run_from_argv
self.execute(*args, **cmd_options)
File "/usr/share/hue/build/env/lib/python3.6/site-packages/django/core/management/base.py", line 398, in execute
output = self.handle(*args, **options)
File "/usr/share/hue/build/env/lib/python3.6/site-packages/django/core/management/base.py", line 89, in wrapped
res = handle_func(*args, **kwargs)
File "/usr/share/hue/build/env/lib/python3.6/site-packages/django/core/management/commands/migrate.py", line 75, in handle
self.check(databases=[database])
File "/usr/share/hue/build/env/lib/python3.6/site-packages/django/core/management/base.py", line 423, in check
databases=databases,
File "/usr/share/hue/build/env/lib/python3.6/site-packages/django/core/checks/registry.py", line 76, in run_checks
new_errors = check(app_configs=app_configs, databases=databases)
File "/usr/share/hue/build/env/lib/python3.6/site-packages/django/core/checks/urls.py", line 13, in check_url_config
return check_resolver(resolver)
File "/usr/share/hue/build/env/lib/python3.6/site-packages/django/core/checks/urls.py", line 23, in check_resolver
return check_method()
File "/usr/share/hue/build/env/lib/python3.6/site-packages/django/urls/resolvers.py", line 413, in check
messages.extend(check_resolver(pattern))
File "/usr/share/hue/build/env/lib/python3.6/site-packages/django/core/checks/urls.py", line 23, in check_resolver
return check_method()
File "/usr/share/hue/build/env/lib/python3.6/site-packages/django/urls/resolvers.py", line 412, in check
for pattern in self.url_patterns:
File "/usr/share/hue/build/env/lib/python3.6/site-packages/django/utils/functional.py", line 48, in get
res = instance.dict[self.name] = self.func(instance)
File "/usr/share/hue/build/env/lib/python3.6/site-packages/django/urls/resolvers.py", line 607, in url_patterns
raise ImproperlyConfigured(msg.format(name=self.urlconf_name)) from e
django.core.exceptions.ImproperlyConfigured: The included URLconf '<module 'libsaml.urls' from '/usr/share/hue/desktop/libs/libsaml/src/libsaml/urls.py'>' does not appear to have any patterns in it. If you see valid patterns in the file then the issue is probably caused by a circular import.

Steps to reproduce it:
Use the default configuration file,
activate the saml backend
and configure it this way:
[libsaml]

base_url="https://..."

create_users_on_login=false

metadata_file="/opt/application/hue/current/security/saml/metadata.xml"

key_file="/opt/application/hue/current/security/saml/key.pem"

cert_file="/opt/application/hue/current/security/saml/certificate.pem"

username_source=attributes
name_id_format="urn:oasis:names:tc:SAML:2.0:nameid-format:persistent"

user_attribute_mapping='{"uid":"username"}'

logout_requests_signed=true

logout_enabled=true

Hue version: 4.10.0 inside a docker container

Can you help me ?

InvalidPointer · 2021-09-27T13:36:35Z

InvalidPointer
Sep 27, 2021

Same issue here. @max-l-f have you found a way to deal with it?

0 replies

max-l-f · 2021-09-27T14:52:50Z

max-l-f
Sep 27, 2021
Author

No I haven't, for now I'm still using hue version 4.8.0 but I was hoping to get some help here

0 replies

InvalidPointer · 2021-09-28T10:35:44Z

InvalidPointer
Sep 28, 2021

@romainr please, could you provide any help here?

0 replies

InvalidPointer · 2021-09-28T13:13:10Z

InvalidPointer
Sep 28, 2021

@max-l-f fixed this by adding djangosaml2==0.18.1 into desktop/core/requirements.txt.

0 replies

max-l-f · 2021-09-28T13:27:26Z

max-l-f
Sep 28, 2021
Author

@InvalidPointer thank you I'll test that

0 replies

InvalidPointer · 2021-09-28T16:17:12Z

InvalidPointer
Sep 28, 2021

I think there are some other fixes should be made in Dockerfile, I'll test them and will also post here.

0 replies

InvalidPointer · 2021-09-28T18:20:55Z

InvalidPointer
Sep 28, 2021

Also needed to add xmlsec1 to apt-get install section at the beginning of Dockerfile.

5 replies

SBatais Nov 15, 2021

@InvalidPointer : Did you succeeded to start HUE 4.10 in a docker container, after the apply of your suggestions ?

InvalidPointer Nov 15, 2021

Yes, I've managed to run HUE 4.10 in a docker container. Had some troubles on my side regarding SAML configuration, here are some useful notes regarding keys: https://docs.cloudera.com/documentation/enterprise/6/6.3/topics/hue_sec_saml_auth.html

Warning: Add key and cert files even if not encrypting assertions. Hue checks for the existence and validity of these files even if they are not needed! They cannot be empty files. This is a known issue.
If necessary, create "valid" dummy files: ...

SBatais Nov 15, 2021

I tried to start HUE 4.10 inside a docker container, and it seems that I have some issues with xmlsec, even if I have already installed xmlsec1 with apt-get install xmlsec1=1.2.25-1build1

[15/Nov/2021 14:41:17 +0100] middleware   INFO     Processing exception: xmlsec binary not found: b'/usr/bin/xmlsec1': Traceback (most recent call last):
  File "/usr/share/hue/build/env/lib/python3.6/site-packages/django/core/handlers/base.py", line 181, in _get_response
    response = wrapped_callback(request, *callback_args, **callback_kwargs)
  File "/usr/lib/python3.6/contextlib.py", line 52, in inner
    return func(*args, **kwds)
  File "/usr/share/hue/build/env/lib/python3.6/site-packages/djangosaml2/views.py", line 517, in metadata
    conf = get_config(config_loader_path, request)
  File "/usr/share/hue/build/env/lib/python3.6/site-packages/djangosaml2/conf.py", line 70, in get_config
    return config_loader(request)
  File "/usr/share/hue/desktop/libs/libsaml/src/libsaml/saml_settings.py", line 106, in config_settings_loader
    'accepted_time_diff': libsaml.conf.ACCEPTED_TIME_DIFF.get(),
  File "/usr/share/hue/build/env/lib/python3.6/site-packages/saml2/config.py", line 337, in load
    self.load_complex(cnf)
  File "/usr/share/hue/build/env/lib/python3.6/site-packages/saml2/config.py", line 271, in load_complex
    self.setattr("", "metadata", self.load_metadata(cnf["metadata"]))
  File "/usr/share/hue/build/env/lib/python3.6/site-packages/saml2/config.py", line 385, in load_metadata
    disable_ssl_certificate_validation=disable_validation)
  File "/usr/share/hue/build/env/lib/python3.6/site-packages/saml2/mdstore.py", line 998, in __init__
    self.security = security_context(config)
  File "/usr/share/hue/build/env/lib/python3.6/site-packages/saml2/sigver.py", line 1029, in security_context
    raise SigverError(err_msg)
saml2.sigver.SigverError: xmlsec binary not found: b'/usr/bin/xmlsec1'

@InvalidPointer : Did you encountered the same problem ?

InvalidPointer Nov 15, 2021

I think I fixed it by adding xmlsec1 to apt-get install section, after that I haven't seen this problem.

SBatais Nov 17, 2021

I have created a forked project of the master and I have added the following things in order to build my own hue docker image:

djangosaml2==0.18.1 into desktop/core/requirements.txt
installation of the apt package xmlsec1 and libxmlsec1-openssl into apt-get install section of hue/tools/docker/hue/Dockerfile

I always have the same problem:

...
  File "/usr/share/hue/build/env/lib/python3.6/site-packages/saml2/sigver.py", line 1029, in security_context
    raise SigverError(err_msg)
saml2.sigver.SigverError: xmlsec binary not found: b'/usr/bin/xmlsec1'

@InvalidPointer : did you change something else ?

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Issue when activating saml backend with hue 4.10.0 inside a docker container #2618

{{title}}

Replies: 7 comments 5 replies

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

Select a reply

Issue when activating saml backend with hue 4.10.0 inside a docker container #2618

Replies: 7 comments · 5 replies

max-l-f Sep 27, 2021 Author

max-l-f Sep 28, 2021 Author

Replies: 7 comments 5 replies

max-l-f
Sep 27, 2021
Author

max-l-f
Sep 28, 2021
Author