How to solve block in RRDI setup ?
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.
2 answers
Comments
Don't think DB2 is configured with SSL....
db2 get dbm cfg |grep SSL
SSL server keydb file (SSL_SVR_KEYDB) =
SSL server stash file (SSL_SVR_STASH) =
SSL server certificate label (SSL_SVR_LABEL) =
SSL service name (SSL_SVCENAME) =
SSL cipher specs (SSL_CIPHERSPECS) =
SSL versions (SSL_VERSIONS) =
SSL client keydb file (SSL_CLNT_KEYDB) =
SSL client stash file (SSL_CLNT_STASH) =
Ahh, I jumped into conclusion. The way to circumvent the problem is mentioned in this article.
I thought I tried that to no avail. I'm trying again; is there a way to "reset" the setup to the point of fresh install w/o having to uninstall/re-install. I have tried:
empty conf/jts/teamserver.properties
cleaning tomcat/work/Catalina/localhost
Hello Kevin,
I think some of the data of the setup application is saved in the Derby repository used by its JTS.
I don't know how to cleanly restore it though.
Best Regards
Francesco
Well, I removed the server directory from the setup tool and copied from another install location which was yet untouched. Then I visited the setup URI under https, not http. Seems to be moving along nicely now.