Mapped attribute generating null value results in Uncaught runtime exception

Losen, Stephen C (scl) scl at virginia.edu
Tue Jan 8 06:42:04 EST 2019


Hi folks,

I created issue IDP-1389 for this.

Stephen C. Losen
ITS - Systems and Storage
University of Virginia
scl at virginia.edu    434-924-0640


-----Original Message-----
From: users [mailto:users-bounces at shibboleth.net] On Behalf Of Losen, Stephen C (scl)
Sent: Monday, January 07, 2019 7:42 AM
To: Shib Users <users at shibboleth.net>
Subject: Mapped attribute generating null value results in Uncaught runtime exception

Hi folks,

Just curious, I ran into some unexpected values in our LDAP such that a Mapped attribute generated a null value.  I had a pattern match like this: "prefix:(.*)" with a return value of "$1".  Some LDAP records had the value "prefix:" so then $1 was empty and that raised an uncaught runtime exception. Had to turn logging up to DEBUG to track it down. Would be less harsh if the IDP simply did not add the null value to the result and continued, perhaps logging a warning.

I fixed my problem with "prefix:(.+)".

This is IDP 3.4.2.

Stephen C. Losen
ITS - Systems and Storage
University of Virginia
scl at virginia.edu    434-924-0640


-- 
For Consortium Member technical support, see https://wiki.shibboleth.net/confluence/x/coFAAg
To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net


More information about the users mailing list