Authentication Error in Rational Build Forge
Hi,
We are experimenting problems trying to connect Build Forge with an Build Forge agent installed on a Oracle Linux Server release 5.9, we have configured a Server and an Authentication in Rational Build Forge, the password configured in the Build Forge's Authentication and the password that we have to enter to the system are the same. We have set up the property magic_login in the bfagent.conf file with the hash obtained using bfagent -P <password>, the port 5555 is open and using telnet, the connection is established. The problem comes when we try to connect Build Forge and the agent from Build Forge, pressing the Test Connection button, this is the output: Host: host.name:5555 Versión de agente: 7.1.3.4-0-0006 Autenticación: AgentMsgAuthUnknownUser Plataforma: linux 2.6.39-400.215.10.el5uek #1 SMP Tue Sep 9 22:51:46 PDT 2014 Estado: Anomalía de autenticación Duración: 0200 HELLO - BuildForge Agent v7.1.3.4-0-0006 320 AUTH AuthFail[*AuthUnknownUser,"usrational"] com.buildforge.services.common.api.APIException: CRRBF0158I: Unable to set user account to unknown account (usrational) at com.buildforge.services.common.ServiceException.(ServiceException.java:37) at com.buildforge.services.common.api.APIException.(APIException.java:24) at com.ibm.jas.mjc.server.refresh.AgentServerTestFiber.checkAuth(AgentServerTestFiber.java:420) at com.ibm.jas.mjc.server.refresh.AgentServerTestFiber.onPingReply(AgentServerTestFiber.java:442) at com.ibm.jas.mjc.server.refresh.AgentServerTestFiber.onReadAgentReply(AgentServerTestFiber.java:231) at com.ibm.jas.agent.AgentFiber.onReadAgentConnectionSuccess(AgentFiber.java:172) at com.ibm.jas.agent.action.ReadAgentConnection.action(ReadAgentConnection.java:50) at com.ibm.jas.fiber.FiberAction.call(FiberAction.java:197) at com.ibm.jas.fiber.action.flow.Block.action(Block.java:63) at com.ibm.jas.fiber.FiberAction.call(FiberAction.java:197) at com.ibm.jas.fiber.action.flow.Block.action(Block.java:63) at com.ibm.jas.fiber.FiberAction.call(FiberAction.java:197) at com.ibm.jas.agent.AgentFiber.action(AgentFiber.java:233) at com.ibm.jas.agent.AgentFiber$AgentFiberAction.action(AgentFiber.java:336) at com.ibm.jas.fiber.FiberAction.call(FiberAction.java:197) at com.ibm.jas.fiber.Fiber.runFiber(Fiber.java:670) at com.ibm.jas.fiber.FiberThread.runFibers(FiberThread.java:258) at com.ibm.jas.fiber.FiberThread.run(FiberThread.java:246) As an additional note: This configuration was working properly, It stopped working between the execution of one job and another. The version of Build Forge is: 7.1.3.4. Thank you very much Vidal Díaz
|
One answer
There are many causes for this issue and therefore you may need to take different actions depending on where the root cause is. The following may help:
1. If you are able to SSH to your server, but not authenticate via BuildForge, you may need to check the bfagent PAM file (/etc/pam.d/bfagent/) against the sshd PAM file (etc/pam.d/sshd).
2. You may also have other working environment. In that case, you can copy the bfagent PAM file (/etc/pam.d/bfagent) from the working environment to the environment that is not working.
3. Make sure you reset the unsuccessful login count in your environment to 0:
bfagent -f /etc/bfagent.conf
/etc/init.d/xinetd restart
pam_tally2 -u <functional id> #to check the unsuccessful login count
pam_tally2 -u <functional id> --reset
3. Have your Linux Server Administrator to review etc/pam.d/system_auth and make sure you have not configured lockout for multiple failed authentications. This is particularly important if you start seeing this issue after changing the password.
4. Check your system messages log when the agent authentication fail and have them reviewed by your Linux administrator.
5. Restart your BuildForge Server and Agent
|
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.