It's all about the answers!

Ask a question

Integrating RTC and Github

Elaine Humphreys (2337) | asked Nov 14 '16, 4:12 a.m.
I am trying to integrate RTC and Github using the 'Register a Git Repository' option in RTC 6.0.2 but am getting a permissions error:

The 'Repository Registration' operation cannot be completed. Permission is required to complete the operation.ID CRJAZ6053E

I am an admin for the RTC project.


2 answers

permanent link
Arun K Sriramaiah (3.2k13477) | answered Nov 14 '16, 6:44 a.m.
Hi Elaine,

I see that its permission issue. Please find the link below and verify the permission and authorization.

Defining Git-related permissions and preconditions

Registering Git repositories

There are two options for authorizing GitHub requests:

A team that pushes commits is authorized for Git operations. For more information, see Authorizing Git requests.
For GitHub Enterprise, a secret key is specified, either during Rational Team Concert™ Git registration or in the GitHub web hooks settings. In this scenario, Rational Team Concert validates that the digest of the payload calculated using the secret key is the same as sent by GitHub in the header of the message. If so, no explicit user authorization is required.


Elaine Humphreys commented Nov 16 '16, 7:37 a.m. | edited Jul 21 '17, 3:27 p.m.

Thanks for sending those links Arun - they were very helpful however after following the setup I have not been able to link pushes on Git to RTC. I have outlined what I have done below:

(1) Registered a Git repository specifying:
        (a) the url to the git repos
        (b) selecting a controlling project area to be the parent project are for the project I owrk on
        (c) selecting a 'Secret Key Auth' - copied the key generated by RTC and linked to the key attribute under the 'Secret Key auth' text area - is this the correct key to use for secret key?
        (d) In settings I have not set Commit URI Format or Namespace prefix for User Branches - I did enter my credentials for Git Server Auth though. I had this authentication specified before I started using the secret key approach.

(2) Added a Webhook in Git specifying:
        (a) payload URL as https://ccm/service/<my secret key from above>. this URL differs to the one specified at - Git was complaining about the 'https://:/' at the start of the payload on this page.
       (b) content type = application/json
       (c) Added my secret key
       (d) selected just push event
       (e) selected 'Active'

I then added a file to my git repos, commited the file using the command git commit -m "Complete task 89802", where 89802 is the task number in RTC, and then did  a git push.

When I open the task there is no change set linked to the task.

Any help would be greatly appreciated as I need to get this integration in place by the end of this week.

Thanks again.

Arun K Sriramaiah commented Nov 16 '16, 7:48 a.m.

Please check below link.

Elaine Humphreys commented Nov 16 '16, 9:59 a.m. | edited Jul 21 '17, 3:27 p.m.

Also Arun - we are using GitHub enterprise  -so from docs I am not sure if we need to install the rtc hooks on git server - expect we do but want to confirm this.

permanent link
Elaine Humphreys (2337) | answered Nov 16 '16, 9:51 a.m.
Hi Arun -

Many of our team will not use Eclipse for commits - we expect team members will use a variety of tools and for now all are using git cli. Therefore can I skip the section 'Execution of CLM-Git Integration use case'? I expect I need [and have not set up as yet] the hooks on the git server - explained in section 'How to configure Hooks on Git server'. this section does not provide the links to the hooks on - could you send the link to me?

Thanks again.

Best Regards,

Your answer

Register or to post 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.