I have added a screenshot of the console output that display the error message that we got.

I can send you via mail the paramfile that the build is using, if you want too.

Hi roy_lu

Is there any update regarding this issue?

Br

Sami

please, is there any update on this ticket? we weren't able to execute our test for more than a week. If there are no solution coming out before Tuesday 2020-01-26 then we will have no choice but to stop using Micro Focus since there are obviously not reliable.

/Sami

Hi Sami,

As a first note and for further usage of the plugin, next time when you encounter an issue which blocks your automation testing processes, please open a CPE with the help of our support engineers. In this way, your ticket will be prioritized over Jira tickets and we can follow up work on the issue easier and establish meetings with you if needed.
Second item, I will take a look on this problem you are facing, since it is related to the jenkins plugin, so it should be handled by us, not by the ALM team.
Indeed compared to version 6.2 there has been a major update regarding the ALM credentials: the ALM credentials, both SSO and non-SSO, have been moved to Jenkins Configure System page. I assume you run the "Migrate ALM credentials job" before using them in your ALM job configuration page. Please make sure that you have both ALM Api key secret and ALM Client ID in Jenkins Configure System page and that they are setup properly also in UFT and still working ( both client ID and api key secret are still valid credentials - make a test a login separately with them in ALM).
If everything is setup correctly and connection with ALM is working outside the Jenkins plugin, we can setup a meeting if you want. Just let me know your availability and preference on Teams or Webex.

You can also email me directly to: anda-sorina.laakso@microfocus.com.

Note: send me by email also the param file ( props....txt).

Here is our updated documentation on using UFT, Jenkins and ALM :

https://admhelp.microfocus.com/uft/en/15.0-15.0.2/UFT_Help/Content/User_Guide/Jenkins.htm#mt-item-8

Thank you.

Hi Sorina

Did you receive the mail that I have send you last week?

Br

Sami

That is strange, I have send an email on Tuesday, 26 January 2021 at 10:06 am to the mail address that you have mention (anda-sorina.laakso@microfocus.com) with the subject "JENKINS-64640 Connect to ALM SaaS via API Key does not work anymore". I will try to send it again.

The situation have not change, some project are using the old version of the plugin (6.2) since the latest version does not wor for them.

I just sent you an email on ajroudsami@gmail.com. Let me know if you received it.

I have received the email and have send you a respons

/sami

Bug fixed.

the issue still occur in version: 6.7 so my question is under which releasing are you going  release this bug fix?

Any updates please....

Please contact Anda, on  anda-sorina.laakso@microfocus.com e-mail address in order to set up a meeting for this blocking issue.

Hi

I have already send email to Anda on the 26 mars 2021 but did not get respond, that is why I have reopened this ticket

Br

Sami 

ajroudsami , is your Domain and Project names are correct? make sure they're with the same casing. it is case-sensitive I too saw this problem and I am able to login after fixing that

you can try this testing it out credentials from https://hostname/qcbin/rest/oauth2/login from postman

headers - Content-Type : application/json
body - 

this is to validate your credentials