Authorizing Git requests in RTC in RTC 6.0.1 and later versions
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).
|
One answer
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. Yes timeout is set to indefinite validity. So, it won't expire until authorization is revoked. |
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.