> I’m using CAS with the SAML protocol and I just realized that the attributes > of the Principal instance are not serialized by the CAS server before they > are send to the client.
That sounds right. I don't think we have a use case for any attribute that doesn't have a reasonable string representation. What kind of object is this? > I would expect such a serialization would have been made given these > attributes are of type Map<String, Object> and not Map<String, String>. I will argue for Map<String, String> for some future version of CAS. We simply don't have a use case for anything that doesn't have a straightforward string representation. I say this with confidence based on the LDAP spec in which everything is a string or base64-encoded string of bytes. Perhaps we do need some facility for attribute transformations that you could leverage in this case to serialize the object before it gets dumped in the attribute map. I've been interested in such a feature for some time, so I'd be happy to create a Jira issue to track it for some future release. > Do you know any update which will correct this situation ? No. I believe the assumption of the OpenSAML libs is that all attributes ought to provide a meaningful string representation. M -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-dev
