3.4.4 errors

[Peter Schober]

* Lalith Jayaweera <ljayaweera at gmail.com> [2019-07-05 10:01]:
> Core attributes available and of course some attributes can be null for
> some users,
[...]
> [net.unicon.idp.externalauth.ShibcasAuthServlet:88] - Something unexpected happened
> 
> net.shibboleth.utilities.java.support.logic.ConstraintViolationException:
> Attribute value cannot be null or empty

I don't know anything about CAS or the Unicon extension to integrate
an external CAS server with the Shiboleth IDP (which seems to be where
this error comes from) but why is it "of course" to be expected that
attribute values are null or empty?

Technologies like LDAP and also SAML are probably coloring my thinking
but with those attributes should simply not be populated (i.e., they
should be absent) and not present-but-without-a-value.
(SQL is an obvious exception but this error is not from an SQL query.)

Maybe your CAS server shouldn't be adding "null or empty" attributes
to the CAS protocol messages either? (Asuming that's what happen, I'm
merely guessing from your message.)

-peter