It's all about the answers!

Ask a question

Authorizing Git requests in RTC in RTC 6.0.1 and later versions


Andre Gusmao (801631) | asked Sep 14 '17, 9:47 p.m.

Up until RTC version 6.0, Knowledge Center says that the authorization for Git requests is valid until you revoke it, the server is restarted, or the OAuth token expires because of a timeout (https://www.ibm.com/support/knowledgecenter/SSYMRC_6.0.0/com.ibm.team.connector.cq.doc/topics/t_git_auth_req.html).

Starting in RTC version 6.0.1, Knowledge Center says that the authorization for Git requests is valid until you revoke it (https://www.ibm.com/support/knowledgecenter/SSYMRC_6.0.1/com.ibm.team.connector.cq.doc/topics/t_git_auth_req.html). Notice that it no longer mentions the cases when the server is restarted or when the OAuth token expires because of a timeout.

My question is: In RTC version 6.0.1 and later versions, does the authorization expires in case of a server restart  or in case the OAuth token expires because of a timeout?

Thanks!

One answer



permanent link
Karthik N V S (563) | answered Sep 15 '17, 8:16 a.m.
JAZZ DEVELOPER

Starting 6.0.1 the  user authorization is persisted across server restarts. So, authorization would not expire in case of server restart.

Related work item 367264


Comments
Andre Gusmao commented Sep 15 '17, 10:43 a.m.

Hi Karthik, thanks for the quick answer. What about the scenario when the OAuth token expires because of a timeout? Has it changed from 6.0 to 6.0.1? Knowledge Center doesn't say anything about the OAuth token expiration in 6.0.1.


Karthik N V S commented Sep 19 '17, 2:33 a.m.
JAZZ DEVELOPER

 Yes timeout is set to indefinite validity. So, it won't expire until authorization is revoked.

Your answer


Register or to post your answer.