New CAS metadata support in 3.4
cantor.2 at osu.edu
Tue Nov 27 09:57:17 EST 2018
On 11/27/18, 9:19 AM, "Cantor, Scott" <cantor.2 at osu.edu> wrote:
> That wouldn't be what I would expect so either the metadata's not right or there's another bug somewhere. Or it's
> connected to the decision made about what the CAS requester is.
You might want to verify you have the metadata correct by using a SAML example as a test case, but I suspect the problem has to do with a different issue than the behavior Marvin coded. The CAS flow probably isn't populating the filter context structure with the SAML metadata even in the case where the metadata is being used, and that would be a bug outright, not anything deliberate in terms of interpretation.
More information about the users