Criterion check bug in AbstractPipelineHttpSOAPClient
Basics
Logistics
Basics
Logistics
Description
I think there's a simple bug at the very bottom of org.opensaml.soap.client.http.AbstractPipelineHttpSOAPClient where it's checking for an existing UsageCriterion before injecting a default, and it's looking for UsageType.class instead of UsageCriterion.class
I didn't want to guess at it, but suspect it's the obvious mistake.
Environment
None
Activity
Brent Putman
January 17, 2020 at 4:21 PM
Fixed on master: 4a54db2e7b692e842d071ed1cb45042be1cc61f3
I think there's a simple bug at the very bottom of org.opensaml.soap.client.http.AbstractPipelineHttpSOAPClient where it's checking for an existing UsageCriterion before injecting a default, and it's looking for UsageType.class instead of UsageCriterion.class
I didn't want to guess at it, but suspect it's the obvious mistake.