forked from arekinath/esaml
-
Notifications
You must be signed in to change notification settings - Fork 49
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
Artifact resolution #10
Comments
I think I am getting confused with terminology. SAML, Shibboleth, and federation. My vague understanding was that Shibboleth = SAML + federation extensions. However this doesn't appear to be correct because this project I believe supports shibboleth but not federation. Anybody able to clear up my confusion as to what the terms mean? Thanks |
For that matter, what is an artifact? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As discussed here: handnot2/samly#28
I would like to be able to use samly with AAF - Australian Access Federation. However registration for AAF requires support for Artifact resolution - at least being my understanding.
The only recommended solution by AAF is to use the Apache shib module, which is a lot of overhead for a docker container and gets confused easily with a Docker environment (been there done that). I would like to be able to attempt to simplify this.
The text was updated successfully, but these errors were encountered: