Hi Rich,
Here is the attachment.
Thanks
Hey ajitzephyr
thanks for the attachment - sorry - even though I've set Chrome to not allow re-directs - it's ignoring the setting for some reason.
Hey ajitzephyr
I was going to try reproducing the issue by using my own project's JIRA/Zephyr instance, but I finished my current contract and got locked out at 6pm, so I can't try and reproduce. However - I grabbed the secretKey and accessKey cos I wanna try and build it cos I still might spot something
Did you follow the instructions EXACTLY or did you deviate at all? (sorry I don't mean to be condescending - I'm just trying to work through the 'possibles' considering I cant try reproducing now) JIRA instructions change quite a bit over versions and the help online can often point to older versions .
You're getting a 401 so it's not even getting to parse your request - I'd guess there's a problem with the Authorization header on the request. even though I can't reproduce I'd like to get as far as I can - it might help diagnose the problem - I've cloned the zapi-cloud repo - but I haven't got access to the .jar file - would you mind attaching the .jar file to your response please?
Cheers,
Rich
Hey ajitzephyr
Been looking at the sampleJWTGenerator.java. Where did you get this part of the URI from "/public/rest/api/1.0/execution"?
In the screenshotted sampleJWTGenerator.java - there's 2 different URIs specified. in the one the URI is "/public/rest/api/1.0/cycle" and in the later screenshot - the same URI has 2 query parms ("/public/rest/api/1.0/cycle?expand&clonedCycleId=").
Reason I'm asking is that if I'm reading the java correctly (and for once, it doesn't look like martian to me) the jwt string value is generated in part by a method that takes these arguments --> zephyrBaseURL, accessKey, secretKey and accountId and another method that uses the zephyrBaseURL and a URI (whether it's "/public/rest/api/1.0/cycle" or "/public/rest/api/1.0/cycle?expand&clonedCycleId=" or even /public/rest/api/1.0/execution) to generate the final JWT token value.
I could be totally wrong - but I'd still like to nail all the possibilities down until we've found what the cause of your issue is.
Cheers
Rich
