Authentication URL for RQM 3
When adding users to RQM 2, we first create cookies using the following command and URL
$cmd = "curl -k -c cookies.txt \"https://${server}:9443/jazz/authenticated/identity\""; We are now working on adding users to RQM 3, and we are trying different URLs like $cmd = "curl -k -c cookies.txt \"https://${server}:9443/jts/authenticated/identity\""; $cmd = "curl -k -c cookies.txt \"https://${server}:9443/jazz/admin\""; $cmd = "curl -k -c cookies.txt \"https://${server}:9443/jts/admin\""; ... nothing works, and cookies are not created. What is the difference between RQM 2 and RQM 3 regarding this command? It would be appreciated if someone can give us a clue. |
One answer
|
In RQM 2, we got the following cookies,
# Netscape HTTP Cookie File # http://curl.haxx.se/rfc/cookie_spec.html # This file was generated by libcurl! Edit at your own risk. servername FALSE /jazz TRUE 0 JSESSIONID 1A8DB0648CB1C138865D578EB1BA44D0 servername FALSE /jazz FALSE 0 JazzFormAuth Form servername FALSE /jazz/authenticated/ FALSE 0 X-com-ibm-team-foundation-auth-loop-avoidance false In RQM 3, the best we can get when using the following command $cmd = "curl -k -c cookies.txt \"https://${server}:9443/jts/authenticated/identity\""; is # Netscape HTTP Cookie File # http://curl.haxx.se/rfc/cookie_spec.html # This file was generated by libcurl! Edit at your own risk. servername FALSE / FALSE 0 WASReqURL https://:9443/jts/authenticated/identity I have no ideal about the cause of the problem. |
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.