It's all about the answers!

Ask a question

Login Failed while connecting to HP ALM in the adaptor.


Arun Batra (14612427) | asked Jun 19 '12, 8:26 a.m.
edited Jun 20 '12, 2:09 a.m.
Hi,

I tried to configure the HP ALM adaptor for CLM and successfully completed the step to exchange the required keys. I was on the help screen (http://my.host.name:8080/hpqc-qm/rest/help/about) and from here, i pressed back button and i was navigated to the screen below. When i tried to login with my HP ALM credentals, it gave the following error. The log file is displayed in the image below.

How to proceed with this? Am i supposed to login with my HP ALM credentials? There is nothing in the documentation about this.

Note that the Edition of HP ALM that i have is "HP Quality Center 11.00 Enterprise". Is it due to this that i am not able to access? i.e the question is regarding the support of this edition by this adaptor.


I Failed to attach an image.
The window in the image was a request to login into HP ALM

And the log was :

156.150.122.52 - - [20/Jun/2012:01:41:35 +0530] "GET /hpqc-qm/rest/catalogs HTTP/1.1" 401 954
156.150.122.52 - - [20/Jun/2012:01:41:35 +0530] "GET /hpqc-qm/rest/catalogs/cm HTTP/1.1" 401 954
156.150.122.52 - - [20/Jun/2012:01:41:35 +0530] "POST /hpqc-qm/rest/oauth/requestToken HTTP/1.1" 200 145
156.150.122.52 - - [20/Jun/2012:01:41:35 +0530] "POST /hpqc-qm/rest/oauth/requestToken HTTP/1.1" 200 145
156.150.122.52 - - [20/Jun/2012:01:41:36 +0530] "GET /hpqc-qm/rest/oauth/authorize?oauth_token=f4557f48-8f03-4672-8788-4d41ea10df81 HTTP/1.1" 200 1933
156.150.122.52 - - [20/Jun/2012:01:41:36 +0530] "GET /hpqc-qm/oauth/scripts/login.js HTTP/1.1" 200 2006
156.150.122.52 - - [20/Jun/2012:01:42:16 +0530] "POST /hpqc-qm/rest/oauth/login HTTP/1.1" 409 95
156.150.122.52 - - [20/Jun/2012:01:44:00 +0530] "POST /hpqc-qm/rest/oauth/login HTTP/1.1" 409 95
156.150.122.52 - - [20/Jun/2012:01:44:50 +0530] "POST /hpqc-qm/rest/oauth/login HTTP/1.1" 409 95
156.150.122.52 - - [20/Jun/2012:01:45:41 +0530] "GET /hpqc-qm/rootservices HTTP/1.1" 200 1960
156.150.122.52 - - [20/Jun/2012:01:45:42 +0530] "GET /hpqc-qm/rest/catalogs HTTP/1.1" 401 954
156.150.122.52 - - [20/Jun/2012:01:45:42 +0530] "GET /hpqc-qm/rest/catalogs/cm HTTP/1.1" 401 954
156.150.122.52 - - [20/Jun/2012:01:45:42 +0530] "POST /hpqc-qm/rest/oauth/requestToken HTTP/1.1" 200 145
156.150.122.52 - - [20/Jun/2012:01:45:42 +0530] "POST /hpqc-qm/rest/oauth/requestToken HTTP/1.1" 200 145
156.150.122.52 - - [20/Jun/2012:01:45:42 +0530] "GET /hpqc-qm/rest/oauth/authorize?oauth_token=3d2e63da-5fde-4f56-a8eb-55b22cad5468 HTTP/1.1" 200 1933
156.150.122.52 - - [20/Jun/2012:01:46:14 +0530] "POST /hpqc-qm/rest/oauth/login HTTP/1.1" 409 95


2 answers



permanent link
Samuel Padgett (2172) | answered Jun 20 '12, 10:58 a.m.
JAZZ DEVELOPER
Hi, Arun. I suspect there is a problem with one of the settings when you first configured the adapter. I'd recommend running through the configuration steps again. You can do this by either deleting or renaming the hpqc-db directory under the apache-tomcat-7.0.26 directory. Note that the administrator ID you specify when settings thing up must be your HP ALM ID or you can't access the setup page again.

You can also enable debug logging to get more information. Stop the server (apache-tomcat-7.0.26/bin/shutdown), then edit the file

apache-tomcat-7.0.26/webapps/hpqc-qm/WEB-INF/classes/log4j.properties

Change the line

log4j.logger.com.ibm.oslc.qm.adapter.hpqc=INFO, stdout, fileappender

to

log4j.logger.com.ibm.oslc.qm.adapter.hpqc=DEBUG, stdout, fileappender

When you start the server again, debug logging will be enabled. This might tell us why the login fails for you.

Just to reiterate Kevin's comment that only HP ALM 11 is supported for the tech preview, and we haven't tested with  the Quality Center Enterprise edition. That could be the cause of the problem.

Thanks and let us know how it goes.

Comments
Arun Batra commented Jun 22 '12, 6:00 a.m. | edited Jun 22 '12, 6:57 a.m.

Hi Samuel, I tried the settings you mentioned but i am still not able to sign in. Could You please mention which log file we should look at to let us know what the error might be as i am not able to locate specific errors in the logs present.


Arun Batra commented Jun 22 '12, 7:11 a.m. | edited Jun 22 '12, 7:11 a.m.

I am starting to believe that the issue might just lie in the variation in version of ALM that i am using here.


Kevin Bauer commented Jun 22 '12, 8:33 a.m.
JAZZ DEVELOPER

Arun, most of the information should go in a hpqc-qm.log file in your tomcat logs directory. Once you turn on logging there. When we try to auth this HP you should see something like "authenticate({the auth point url we try to hit from hp}, userid)" followed by the response we get back from HP.


Kevin Bauer commented Jun 22 '12, 4:21 p.m.
JAZZ DEVELOPER

Arun, We have what HP tells us in Quality Center 11 setup and we are not having any issues authenticating. Would you be interested in working with us to debug this issue via screen share etc?

You can find my email in my jazz dev profile https://jazz.net/jts/admin#action=com.ibm.team.repository.viewUserProfile&itemId=_2L_54DUuEdy9D-RQ62jSnw


permanent link
Kevin Bauer (34621) | answered Jun 19 '12, 9:27 a.m.
JAZZ DEVELOPER
Hello Arun,

I do not see an attached photo of there error / log you are seeing (can you reattach it)?  Once setup you should be able to login to the adapter via your HP userid (one know issue here is that HP does not authorize a user with a null/empty password via their REST API not sure if this is the case).

All our testing for the tech preview was done on HP ALM 11.  It is our understanding that Quality Center 11 is build on the same code base and should work but we did not include this in the support etch preview platforms due to testing.


Comments
Arun Batra commented Jun 19 '12, 11:08 a.m.

I have edited the Question above.. The password is not null or empty string. Another question: If the user will be authenticated from HPQC, then what is the puprose of adding an admin user during the configuration of rootservice URIs, i.e. the first time adaptor is configured?


Kevin Bauer commented Jun 19 '12, 12:19 p.m.
JAZZ DEVELOPER

I still do not see the actual error you are seeing anywhere. So if you go back to main adapter URL (http://my.host.name:8080/hpqc-qm) are you still having an issue logging in with you HP userid or is it just the admin pages?

The purpose of adding an admin user id is to lock who has access to the adapter admin pages (set the base URL, add admin associate friends servers etc). The login should allow any HP user to log in and be able to access entities they have access to.


Arun Batra commented Jun 20 '12, 2:00 a.m.

Yes, When i go to the main adapter URL, i have issue logging in with the my HP user id. The last line in the log states that the URL results in Status Code 409 instead of 200. Is there a log where i can get the details of this? (Detail like: Is the url that is formed during this operation correct or not. It should ideally be https://my.HPQC.hostname/qcbin/authentication-point/authenticate to login into hpqc).


Kevin Bauer commented Jun 22 '12, 10:50 a.m.
JAZZ DEVELOPER

That is the URL we should be trying to construct assuming https://my.HPQC.hostname/qcbin/ is your base URL. With debug turned on hpqc-qm.log should have some more information on the failure.

Your answer


Register or to post 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.