cantor.2 at osu.edu
Fri Jul 5 10:20:37 EDT 2019
On 7/5/19, 4:01 AM, "users on behalf of Lalith Jayaweera" <users-bounces at shibboleth.net on behalf of ljayaweera at gmail.com> wrote:
> Upgraded to above from 3.3.x and got below error
The enforcement rule against null values has been in the code since 3.0.0. The attribute support in the CAS plugin is not that old.
> Core attributes available and of course some attributes can be null for some users,
If the values can be null, then the proper thing to do is to call StringAttributeValue.valueOf(), which produces a number of different object types based on whether the value is null or empty. StringAttributeValue itself does not permit either, so constructing one directly with a null or empty value fails.
i.e. the Unicon code has a bug, you would need to file that with them.
Our APIs all consistently document null requirements, occasional errors notwithstanding. If you call something @Nonnull @NotEmpty with either, you should expect it to fail, and this does.
More information about the users