Mapped attribute generating null value results in Uncaught runtime exception

[Rod Widdowson]

> 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.

Can you put in a case please so it doesn't fall off..

> Would be less harsh if the IDP simply did not add the null
> value to the result and continued, perhaps logging a warning.

That actually doesn't work (because of things like template attributes which need specific number of attribute values), but we do
have the concept of a null attribute value which would seem apposite...

Thanks