Metadata Aggregator 0.9.0: "Error creating bean with name 'httpClientBuilder'

[Steve Thorpe]

Scott & Brent: Many thanks for your feedback. These clues helped me in 
my debugging quest. I was able to make some progress but ultimately I 
saw additional exceptions. It may well be the configuration file for 
Example 3 described in the Metadata Aggregator documentation (see 
https://wiki.shibboleth.net/confluence/display/MA1/3.1+General+Configuration) 
has several issues like this ... a mismatch between current APIs and 
previous APIs. Eventually I was frustrated going into a debugging 
rathole so I decided on an alternate tack that seems to be working in my 
preliminary tests.

Wanted to share the steps I took in case it is helpful to other Metadata 
Aggregator types:


1) Modified this config file for Example 3 to match my local setup
https://wiki.shibboleth.net/confluence/download/attachments/458803/config3.xml


2) Downgraded to the previous MDA release (0.8.0) instead of the latest 
(0.9.0)
http://shibboleth.net/downloads/metadata-aggregator/0.8.0/aggregator-cli-0.8.0-bin.zip


3) Made sure to use saml-schema-metadata-2.0.xsd from this tarball
otherwise it yelled at me with some exception or other. Thanks InCommon
for this!
http://wayf.incommonfederation.org/bridge/docs/schema-files.tar.gz



4) Used Oracle Java 7 (probably any Java 7 or 8 would work but just
for the record wanted to capture the version that worked for me)
     java version "1.7.0_80"
     Java(TM) SE Runtime Environment (build 1.7.0_80-b15)
     Java HotSpot(TM) 64-Bit Server VM (build 24.80-b11, mixed mode)


5) Upped the memory from 512M to Xmx2048M since InCommon's preview
aggregate is too big to be handled with only 512MB.  So for the record
here was my command line invocation of the MDA:
JAVA_HOME=/usr/java/jre1.7.0_80 JMVOPTS=-Xmx2048M ./mda.sh --verbose 
/home/thorpe/fim/mda/config3.xml  main 2>&1 | tee /tmp/java7.output


6) Commented out the signEntitiesDescriptor bits in the config file.
Eventually I am probably going to add this back in, however for now
I just wanted to get data flowing all the way through so I turned
this off for now.



With those steps, voila!!  Example 3 of 
https://wiki.shibboleth.net/confluence/display/MA1/3.1+General+Configuration 
is working for me!!  (except for the signing part that I turned off for 
now).  Description of my modified example 3 is:

"A command line configuration that reads in the /**PREVIEW InCommon MD 
AGGREGATE**/, UK, and local metadata and for each one checks the 
signature (and fails if the signature is bad), validates the validUtil 
constraint, disassembles al EntityDescriptors, and validates the schema 
of each EntityDescriptor. Then all the inputs are merged together and 
schema invalid items logged and removed. Finally, three output streams 
are constructed, one that contains all entities, one that contains only 
IdPs, and one that contains only SP. Each stream is assembled into an 
EntitiesDescriptor, a validUntil constraint is added, and the entire 
thing is /**NOT SIGNED**/ then written out to a file. Also demonstrates 
various ways to remove some of the verbosity of Spring bean files."



To Ian: Thank you very much for sharing this helpful MDA tool!!


Steve

On 2/12/16 3:04 PM, Brent Putman wrote:
>
>
> On 2/12/16 1:32 PM, Cantor, Scott wrote:
>>> If you have any pointers to help resolve this I would be grateful....
>>> hopeing it is an easy fix.  Thanks!
>> Wild guess, but disregardSslX became disregardTlsX I think. I know it did in the IdP.
>
> Yes, per the current java-support HttpClientBuilder, would be:
> connectionDisregardTLSCertificate
>
> I think it changed before IdP 3.x was officially released. The old -Ssl-
> one was removed in the new major version of java-support released at
> same time as IdP 3.0.0.  Sounds like some docs and/or Spring wiring for
> the MDA wasn't updated to reflect this when the MDA was bumped to use
> the new java-support major version.  Note: we don't remove API's outside
> of a major release bump.


-- 
Steve Thorpe
Systems Programmer/Analyst, MCNC
Email: thorpe at mcnc.org
Office: 919-248-1161
Mobile: 919-724-9654
Skype/AIM: thorpe682

Connecting North Carolina's Future Today