Hi all, I'm using CAS as my IDP for InCommon and it is working fine. I have no insurmountable issues since the transition from Shibboleth. One quirky thing that I am hoping that there is a way to reduce the complexity of the individual service definition files is to externalize the creation of the eduPersonTargetedID.
I'd like for the folk I've asked to manage the service not to have to add this configuration over and over. CAS - SAML2 Attribute Release | Releasing eduPersonTargetedID <https://apereo.github.io/cas/6.5.x/installation/Configuring-SAML2-Attribute-Release.html#releasing-edupersontargetedid> I'm using CAS - Attribute Definitions | JSON Attributes Definitions <https://apereo.github.io/cas/6.5.x/integration/Attribute-Definitions.html#json-attribute-definitions> to address the lack of eduPersonScopedAffiliation in my directory. I see it's possible to use groovy from the definition, but I'm not sure how to build the attribute value to pass it back in that context. It is outside my experience with groovy, I have really only needed to build strings for custom attribute values. Has anyone found a way to just make eduPersonTargetedID an attribute that can be added without having to do a merging strategy and explicitly add it to each service definition? Thanks -- - Website: https://apereo.github.io/cas - Gitter Chatroom: https://gitter.im/apereo/cas - List Guidelines: https://goo.gl/1VRrw7 - Contributions: https://goo.gl/mh7qDG --- You received this message because you are subscribed to the Google Groups "CAS Community" group. To unsubscribe from this group and stop receiving emails from it, send an email to cas-user+unsubscr...@apereo.org. To view this discussion on the web visit https://groups.google.com/a/apereo.org/d/msgid/cas-user/d37dea3f-dc4e-4ffe-a4c2-bde23ba2773bn%40apereo.org.
