Hi, I have not done it myself but it should be straightforward. It is just a WSGI app so if you know how to "mount" WSGI apps into Apache using mod_wsgi you should be able to get it going without too much trouble. I usually just run it with the gunicorn server but than that sits behind a load balancer (either Amazon ELB or HA proxy), and it works just fine in that configuration. Others on the list may have direct experience or tips to share with you. Cheers, Scott K

I could share a example nginx configuration if you need.

Here your are: The particular nginx server definition in /etc/nginx/server.d/: https://github.com/rhoerbe/satosa-proxy5/blob/master/config_nginx/proxy.con… Which is part of a more general configuration: https://github.com/rhoerbe/satosa-proxy5/blob/master/config_nginx/proxy.con…

Thanks Rainer, Another question, I am trying to setup a proxy with Dynamics 365 Portal as SP and SWAMID metadata as IdP. My intention is to use SWAMID/NORDUNET discovery service for IdP discovery. We will add a web server in front of the proxy later. Our configs for SAML2SAML are on GitHub link below, using self signed certificates (https, metadata, frontend and backend, 4 pairs, not included), however, I can not get any success. Am I missing anything fundamental? Thanks https://github.com/ifmsasweden/s2s <https://github.com/ifmsasweden/s2s> docker run -p 443:8000 -v /home/ifmsa/s2s:/opt/satosa/etc -e DATA_DIR=/opt/satosa/etc -e PROXY_PORT=8000 -e METADATA_DIR=metadata satosa/satosa Writing metadata to 'metadata/frontend.xml' Writing metadata to 'metadata/backend.xml' [2017-09-17 10:34:03 +0000] [1] [INFO] Starting gunicorn 19.7.1 [2017-09-17 10:34:03 +0000] [1] [INFO] Listening at: https://0.0.0.0:8000 (1) [2017-09-17 10:34:03 +0000] [1] [INFO] Using worker: sync [2017-09-17 10:34:03 +0000] [19] [INFO] Booting worker with pid: 19 [2017-09-17 10:34:04] [INFO ]: Loading backend modules... [2017-09-17 10:34:23] [INFO ]: Setup backends: ['Saml2'] [2017-09-17 10:34:23] [INFO ]: Loading frontend modules... [2017-09-17 10:34:23] [INFO ]: Setup frontends: ['Saml2IDP'] [2017-09-17 10:34:23] [INFO ]: Loading micro services... [2017-09-17 10:34:23] [INFO ]: Loaded request micro services: [] [2017-09-17 10:34:23] [INFO ]: Loaded response micro services: ['AddStaticAttributes'] [2017-09-17 10:34:24] [DEBUG]: Loaded backends with endpoints: [<satosa.backends.saml2.SAMLBackend object at 0x7f8b2e900c50>] [2017-09-17 10:34:24] [DEBUG]: Loaded frontends with endpoints: [<satosa.frontends.saml2.SAMLFrontend object at 0x7f8b2defb940>] [2017-09-17 10:34:24] [DEBUG]: Loaded micro services with endpoints: [<satosa.micro_services.attribute_modifications.AddStaticAttributes object at 0x7f8b2defb780>] [2017-09-17 10:36:26] [DEBUG]: read request data: {} [2017-09-17 10:36:26] [DEBUG]: Did not find cookie named 'SATOSA_STATE' in cookie string '' [2017-09-17 10:36:26] [DEBUG]: [urn:uuid:cb482c60-12c8-4d3a-b954-007c7e5e7fd6] Routing path: Saml2IDP/proxy.xml [2017-09-17 10:36:26] [DEBUG]: [urn:uuid:cb482c60-12c8-4d3a-b954-007c7e5e7fd6] Unknown backend Saml2IDP

Thanks Rainer. Is "Discovery Service” a "work out-of-box” solution, or doe it need any extra config, the SP we are using against the Proxy can otherwise neither use a Discovery or consume metadata with multiple IdPs (and no signing). Regards Mats