Provide TU Wien SP configuration as example

[max-moser]

Idea

We're using SATOSA as part of our authentication pipeline for the service provider (SP) TU Wien Research Data, our institutional research data repository. This SP has been registered into the Austrian ACOnet federation, and also the eduGAIN interfederation. We're utilizing the interfederation metadata to allow login with many identity providers (IdP) globally.

I figured that this setup may make for a decent example, especially given that we improved the configuration together with Peter Brand from ACOnet not that long ago.

I intend to be touching up some of the documentation pages to refer to these example configurations, as well as our services in the TU Wien GitLab instance:

• SATOSA setup
• Simple custom discovery service

Checklist

• [x] Have you checked to ensure there aren't other open Pull Requests for the same update/change?
• [x] Have you added an explanation of what problem you are trying to solve with this PR?
• [ ] Have you added information on what your changes do and why you chose this as your solution?
• [ ] Have you written new tests for your changes?
• [ ] Does your submission pass tests?
• [ ] This project follows PEP8 style guide. Have you run your code against the 'flake8' linter?