Provide TU Wien SP configuration as example #469
Draft
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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:
Checklist