Empty static data connector in attribute-resolver.xml results in null exception.
Basics
Logistics
Basics
Logistics
Description
When there are no attribute definitions inside a statid data connector, the following generic error occurs:
ERROR [edu.internet2.middleware.shibboleth.common.config.BaseService:188] - Configuration was not loaded for shibboleth.AttributeResolver service, error creating components. The root cause of this error was: java.lang.NullPointerException: null
There is no hint at all (even on DEBUG level), what is going on.
I've been mostly leaving any V2 bugs alone, and just committing fixes to V3 where they apply, but if we have to do a release quickly because of a security issue, it would be good if minor bugs were already fixed.
Tom Zeller
September 25, 2013 at 4:13 PM
The fix is simple. Attaching a patch to StaticDataConnectorBeanDefinitionParser. A bug like this is a reason for the @Nullable annotation in v3.
When there are no attribute definitions inside a statid data connector, the following generic error occurs:
ERROR [edu.internet2.middleware.shibboleth.common.config.BaseService:188] - Configuration was not loaded for shibboleth.AttributeResolver service, error creating components. The root cause of this error was: java.lang.NullPointerException: null
There is no hint at all (even on DEBUG level), what is going on.