Setting up RRDI (I've done before w/o issue).  This is on an AIX server and I'm running the /rrdi/setup.  Step 1 goes ok, but on step 2 (setting up the content warehouse) I get:

CRRRA0077E: An error happened when validating the database. 'javax.net.ssl.SSLPeerUnverifiedException: peer not authenticated'.

I have tried going into the setup uri both with http, https.  I did alter the ports for the http and https for the setup tool.   I get the expected SSL warning on the setup initialization step.

Thoughts?

p.s.  Seeing this in jts.log:

http-bio-12010-exec-14]  WARN sitory.service.internal.oauth.OAuthServiceProvider  - CRJAZ2115W The consumer application named "RRDI Setup (http://rtp-rrdi:12000/rrdi)" has been registered as "trusted", that is, for this consumer application it is not necessary to present to the user an authorization dialog requesting that user's permission to allow the application to access this server.  However, the callback URL "http://rtp-rrdi:12000/rrdi/oauthCallback?request_token_secret=S1HecWSXuHoVJiFmcCRnaVnXM1L41fvNcJIeFB2yLrg%3D" that was specified for request token authorization cannot be determined by this server to originate from any trusted consumer or application.  So for this authorization cycle, this consumer is not considered trusted and an authorization dialog will be issued. If you (the administrator) wish to assert that this callback is trusted, enter the callbackURL into the OAuthServiceProvider server configuration page section for trusted URIs, per the directions for that field.
2013-05-29 13:13:32,965 [        http-bio-12010-exec-17]  WARN sitory.service.internal.oauth.OAuthServiceProvider  - CRJAZ2115W The consumer application named "RRDI Setup (http://rtp-rrdi:12000/rrdi)" has been registered as "trusted", that is, for this consumer application it is not necessary to present to the user an authorization dialog requesting that user's permission to allow the application to access this server.  However, the callback URL "https://rtp-rrdi:12010/rrdi/oauthCallback?request_token_secret=HPNn7A8ViNPhwedvXlf8uCbWQQE93M89jc%2FAGaDz1R4%3D" that was specified for request token authorization cannot be determined by this server to originate from any trusted consumer or application.  So for this authorization cycle, this consumer is not considered trusted and an authorization dialog will be issued. If you (the administrator) wish to assert that this callback is trusted, enter the callbackURL into the OAuthServiceProvider server configuration page section for trusted URIs, per the directions for that field.

Have tried updating the jts configuration w/o much success.