10:13 a.m.
Thanks Giuseppe for your work!
I appreciate your help. I already had a look at the work but it seems that I need a
further hint:
Could I ask you to elaborate a little on the paths used in your proxy_conf.yaml?
Intended goals:
- Store some custom modules (microservices) on a docker host and mount it to a place in
the docker, e.g. /etc/satosa/modules/
- Use configuration option 'custom_plugin_module_paths' of proxy_conf to load the
custom modules, e.g. - modules
In your Satosa-Saml2Spid/example/proxy_conf.yaml you use a path like
"plugins/micro_services" as 'custom_plugin_module_paths', though this
path seems not relative from the file itself as there is no folder
"plugins/micro_services" in your repo at this location. So this is a different
behaviour compared to the backend/frontend_modules yaml configuration file paths. Those
are listed and located relatively to the proxy_conf.yaml.
If i'd need to take a guess, i'd say that it seems that the paths for custom
modules are relativly to python -> site packages -> satosa. If you build an image
yourself, this would not be too bad, but if you use a prebuild official image, I'd
need to hardcode this (the path incl. the python version) in my docker compose file?
I also saw a hardcoded python-version-based path to site packages of satosa in the
demo-run/run shell file.
Btw. I use a docker compose and the original non-modified image.
Regards
canni