ljayaweera at gmail.com
Sun Jul 7 08:16:13 EDT 2019
This failure started only after the IdP upgrade, CAS version remain as is,
and no other change except IdP version upgrade,
I was able to see the CAS service validate URL has been changed to 3.0
protocoal https://<CAS HOST>/cas/p3/serviceValidate in the call from IdP to
With previous IdP version 3.3.x it was CAS2.0 protocol with URL https://<CAS
HOST>/cas/serviceValidate and it worked without issues
So in the new IdP version I added below config in the idp.properties
assuming it will work as it is CAS20 but still it failed with the same ERROR
shibcas.ticketValidatorName = cas20
On Sat, Jul 6, 2019 at 12:21 AM Cantor, Scott <cantor.2 at osu.edu> wrote:
> 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.
> -- Scott
> For Consortium Member technical support, see
> To unsubscribe from this list send an email to
> users-unsubscribe at shibboleth.net
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the users