Build Forge Build Engine Test Connection failing
Robert Frenette (1●1●1)
| asked Jan 24 '14, 3:02 p.m.
edited Jan 31 '14, 12:03 p.m. by Nick Edgar (6.5k●7●11)
I've created a Build Forge Build Engine in RTC, and have the associated buildforge_conf/bfserver_port directories (SSL and Non-SSL ports) containing the bfclient.conf, buildForgeKeyStore.p12 and buildForgeTrustStore.p12 files on the Jazz (4.0.2) server. I've also edited the bfclient.conf files in each dir to point to the absolute paths of the .p12 files.
I entered my credentials (the same I use to successfully log into the Build Forge web client) in the Build Forge Authentication section on the Build Forge Build Engine tab but, when I Test Connection, I get the following: SSL port: Testing, please wait... Result: Failed. A java.io.IOException exception occurred testing the connection. Verify the host and port specified, make sure the Build Forge server is running and retry the connection test. The logs should have more detailed information about the exception. Client closed connection during handshake Non-SSL port: Testing, please wait... Result: Failed. A com.buildforge.services.common.api.APIException exception occurred testing the connection. Verify the user id and password specified and retry. The logs should have more detailed information about the exception. Message[uuid=null, timestamp=1390592470, userUuid=, processId=0, severity=ERROR, type=, componentUuid=null, messageKey=APILoginFailed, indirectionMask=0, args={}] The ccm.log file on the Jazz server indicates: "Error finding Build Forge SSL configuration files" at the absolute paths I specified in the bfclient.conf files, although the paths are correct and the files are there. Does anyone know what I may be missing in my configuration? Thanks for any guidance. |
2 answers
The Help topic has a note about connection settings http://pic.dhe.ibm.com/infocenter/clmhelp/v4r0m5/topic/com.ibm.team.build.doc/topics/t_buildforgeengine.html
Comments
Robert Frenette
commented Jan 31 '14, 7:09 a.m.
Thanks for the post. I had followed the help topic you mentioned to originally create the build engine, associated dirs, and request files from my BF Admin. After reading it again, the following jumps out at me:
|
Nick Edgar (6.5k●7●11)
| answered Jan 31 '14, 11:37 a.m.
JAZZ DEVELOPER edited Jan 31 '14, 11:38 a.m.
Hi Robert, sorry for the delay in responding on this. I suggest tagging RTC Build related issues with 'build', which notifies me and others.
> and have the associated buildforge_conf/bfserver_port directories
The expected layout is:
RTC-SERVER-DIR
buildforge_conf
{BF-HOSTNAME}_{BF-PORT} // as configured in the build engine
bfclient.conf
Where bfclient.conf has absolute paths to the .p12 and .jks files (which are usually siblings to the bfclient.conf file).
Is this what you have? In your post, you mentioned bfserver_port but not the hostname.
Comments
Robert Frenette
commented Jan 31 '14, 11:51 a.m.
Hi Nick,
Does it work when you don't have the SSL option in the RTC BF build engine turned on? The "Error finding Build Forge SSL configuration files" really is specific to the SSL setup and directory layout, and doesn't indicate incorrect credentials. In the code, I missed this earlier, but it does require either the .p12 or .jks file to exist as a sibling of the bfclient.conf file.
The absolute paths in the bfclient.conf file are a factor later (the BF client code we use resolves relative paths relative to the current working directory, which is wrong in our usage).
I have tried both with/without SSL, and neither works. (I do have BF-HOSTNAME_BF_PORT dirs for both SSL and non-SSL.) I also have the bf.conf and .p12 files in those dirs, with absolute paths to the .p12 files..
No, bfclient.conf and .p12 etc should be in the same dir, under {BF-HOSTNAME}_{BF-PORT}
> I have tried both with/without SSL, and neither works.
Do you get the same error in the RTC server log for the non-SSL case? If "Connect securely to Build Forge" is unchecked, it shouldn't even be checking for the buildforge_conf/HOST_PORT dir.
Robert Frenette
commented Jan 31 '14, 1:03 p.m.
Non-SSL port test results:
Is there anything in the RTC server log for the non-SSL test?
showing 5 of 6
show 1 more comments
|
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.