-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Local shibboleth setup #68
Comments
Hi, please assign me to this issue. 🙂 |
Shibboleth is turning out to be extremely finicky to work with. Do we actually need Shibboleth, or can I just configure an Apache server to add a "utorid" header to all requests it proxies? |
Well like we saw in #50 shibboleth can have an impact on how things are working. So it would be nice to mimic this in a dev environment. If it is too unstable, then we can consider using either Apache or maybe a simple node env variable for example: const headers = process.env.NODE_ENV === "production" ? {utorid: "exampl_utorid"} : {} Also let us know what you have tried to setup shibboleth. Maybe we can help you debug. There is a docker image for shibboleth - https://github.com/Unicon/shibboleth-idp-dockerized |
Interesting; I'll see if I can get the docker image to behave. That was basically what I was trying to create from scratch earlier. Thanks. |
Which half of Shibboleth do we care about replicating? The IdP or SP portion? It's a bit unclear to me what the difference is. |
You would need both I believe. Here is good read - https://shibboleth.atlassian.net/wiki/spaces/CONCEPT/overview This example might help set things up - https://github.com/UniconLabs/dockerized-idp-testbed |
Is your feature request related to a problem? Please describe.
For testing currently we have to forcefully add an additional header
utorid
before running the client. The idea here is to explore ways to automate this.Describe the solution you'd like
OR
Additional context
A guide to setup shibboleth locally - https://isea.utoronto.ca/services/weblogin/sso-howto-weblogin/
The text was updated successfully, but these errors were encountered: