Hey Canni, thank you and thank you for sharing! to a place in the docker, e.g. /etc/satosa/modules/ the module must be a python package, installed or importable in the relative path starting from the base directory I use the deploy strategy you see, mounting the configuration folder using a docker volume ;-) with custom module in the projects, otherwise you should package your module and install it via pip/poetry path incl. the python version) in my docker compose file? Satosa-saml2spid has its image here https://github.com/italia/Satosa-Saml2Spid/pkgs/container/satosa-saml2spid the best way to go for you is creating your own module and installing them via python env satosa in the demo-run/run shell file. thank you, deprecated since we're using docker and the that code should be updated with the example in the readme, here: https://github.com/italia/Satosa-Saml2Spid/tree/master#start-the-proxy if you like doing PR you're welcome and that would be really appreciated! that's good, always use official images and when needed take a look to side projects like satosa-saml2spid for any comparison, then come with your questions anytime you want, best Il giorno mar 23 mag 2023 alle ore 10:14 &lt;canni2007(a)gmail.com&gt; ha scritto: > 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: > 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? > > satosa in the demo-run/run shell file. > > > Regards > canni > _______________________________________________ > satosa-users mailing list -- satosa-users(a)lists.sunet.se > To unsubscribe send an email to satosa-users-leave(a)lists.sunet.se > -- ____________________ Giuseppe De Marco Centro ICT d'Ateneo Università della Calabria 87036 Rende (CS) - Italy Phone: +39 0984 496961 e-mail: giuseppe.demarco(a)unical.it -- ------------------------------------------------------------------------------------------------------------------ Il banner è generato automaticamente dal servizio di posta elettronica dell'Università della Calabria <https://www.unical.it/5x1000>