[WIP] Implement (optional) authentication via Shibboleth instead of built-in SAML #32
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Currently the authentication is done via SURF's stepup bundle (integrating saml2 from SimpleSAMLphp in Symfony); this can be a bit limited, and some people may prefer to have the webserver (and entire application) protected by mod_shib, or some other authentication module such as mod_auth_oidc that provides a REMOTE_USER variable to the application.
This is a rough proposal to do this, but it is not configurable.
Nelmio was disabled since it wasn't reachable anyway when the server was protected by Shibboleth.
Todo: