ValueConfiguration differs from IdP v3.x to v4.x?
cantor.2 at osu.edu
Sat May 16 17:37:42 UTC 2020
Also, to clarify what might be happening here...
With V4, the AttributeInMetadata rule is driven by the new Attribute Registry service, which uses a lot of built-in rules to auto-decode SAML Attribute syntax back into local attribute names that would then match up with what you were doing in the IdP.
I would maybe suspect that the issue is that In V3, it wasn't reverse mapping the SP's RequestedAttribute into the "eduPersonEntitlement" name for some reason, and that was preventing the release.
You still had the same declared "intent" in the old version, but it wasn't happening, which coincidentally was better than actually honoring what you told it to do.
It might be useful to dig into why it wasn't reverse mapping it before, but in the end, the point is that the new version is more advanced and capable at that step.
More information about the users