Hi Ian,

Sounds like that auth token may have also been removed. We don't really
have a good way of resetting these for GitLab right now in Review Board.
There's a workaround, but it's not ideal, and we're wanting to build
something nicer for this:

1) Go into the Review Board admin UI -> Database -> Hosting Accounts.
2) Edit the entry for your GitLab account, and temporarily rename the
username.
3) Add a new repository and link your account again. This will be
temporary. You don't even need to specify a valid repository name, since we
don't care if that's created. We just care that the linking process worked.
4) Go back into the Hosting Accounts section, and find the new account.
Copy all the authentication data (it's a JSON payload), and paste it into
the original account.
5) Delete the new one and rename the original one back.

This will basically update the existing linked account, in a round-about
way. In future versions, we'll have a nicer process in place for this (we
have a lot of work in progress for a better repository management
experience).

Let me know if that works!

Christian

-- 
Christian Hammond - christ...@beanbaginc.com
Review Board - https://www.reviewboard.org
Beanbag, Inc. - https://www.beanbaginc.com

On Tue, Dec 15, 2015 at 9:00 PM, Ian <iander...@mac.com> wrote:

> Yeah I just double checked via GitLab's web UI.  The password for the
> shared account has changed since I originally set up the repositories.  I
> tried the "link new account" option and typed in the current username and
> password but it doesn't want to work for some reason.  Our GitLab
> installation has been upgraded a few times too, it's GitLab Enterprise
> Edition 7.14.3-ee 60aabef if that matters.
>
> Ian
>
> On Monday, December 7, 2015 at 1:53:02 AM UTC-8, Christian Hammond wrote:
>>
>> Hi Ian,
>>
>> Can you verify that the username associated with those repositories still
>> has the necessary access permissions on the GitLab server?
>>
>> I checked the code in question, involving repository verification and how
>> credentials are used, and it hasn't changed since 2.0.x, so at this point
>> I'd want to verify the GitLab setup.
>>
>> Christian
>>
>> --
>> Christian Hammond - chri...@beanbaginc.com
>> Review Board - https://www.reviewboard.org
>> Beanbag, Inc. - https://www.beanbaginc.com
>>
>> On Sun, Dec 6, 2015 at 3:11 PM, Ian <iand...@mac.com> wrote:
>>
>>> Any idea on how I could fix this?
>>>
>>> Ian
>>>
>>>
>>> On Tuesday, November 17, 2015 at 4:56:19 PM UTC-8, Ian wrote:
>>>>
>>>> Yes, existing review requests against the repository are loading, I
>>>> just can't change the repository configuration.
>>>>
>>>> Ian
>>>>
>>>> On Monday, November 16, 2015 at 11:30:51 PM UTC-8, Christian Hammond
>>>> wrote:
>>>>>
>>>>> Hi Ian,
>>>>>
>>>>> Do existing review requests against this repository still work? Is
>>>>> this solely when changing the repository configuration?
>>>>>
>>>>> Christian
>>>>>
>>>>> --
>>>>> Christian Hammond - chri...@beanbaginc.com
>>>>> Review Board - https://www.reviewboard.org
>>>>> Beanbag, Inc. - https://www.beanbaginc.com
>>>>>
>>>>> On Mon, Nov 16, 2015 at 7:47 PM, Ian <emai...@gmail.com> wrote:
>>>>>
>>>>>> I recently updated to ReviewBoard 2.5.1 and now I can't change any of
>>>>>> my GitLab repositories, when I do it says "A repository with this name 
>>>>>> was
>>>>>> not found on this group, or your user may not have access to it."  I
>>>>>> verified that I can log into my GitLab installation and see the
>>>>>> repositories from a web browser running on the ReviewBoard server using 
>>>>>> the
>>>>>> same account.  I don't suppose this is a known issue?  My config looks 
>>>>>> like
>>>>>> this.
>>>>>>
>>>>>> Hosting Service: GitLab
>>>>>> Service URL: https://gitlab.domain.com
>>>>>> Account: username
>>>>>> Repository Type: Git
>>>>>> Repository Plan: Group
>>>>>> GitLab Group Name: groupname
>>>>>> Repository Name: repositoryname
>>>>>>
>>>>>> Ian
>>>>>>
>>>>>> --
>>>>>> Supercharge your Review Board with Power Pack:
>>>>>> https://www.reviewboard.org/powerpack/
>>>>>> Want us to host Review Board for you? Check out RBCommons:
>>>>>> https://rbcommons.com/
>>>>>> Happy user? Let us know! https://www.reviewboard.org/users/
>>>>>> ---
>>>>>> You received this message because you are subscribed to the Google
>>>>>> Groups "reviewboard" group.
>>>>>> To unsubscribe from this group and stop receiving emails from it,
>>>>>> send an email to reviewboard...@googlegroups.com.
>>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>>
>>>>> --
>>> Supercharge your Review Board with Power Pack:
>>> https://www.reviewboard.org/powerpack/
>>> Want us to host Review Board for you? Check out RBCommons:
>>> https://rbcommons.com/
>>> Happy user? Let us know! https://www.reviewboard.org/users/
>>> ---
>>> You received this message because you are subscribed to the Google
>>> Groups "reviewboard" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to reviewboard...@googlegroups.com.
>>>
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>> --
> Supercharge your Review Board with Power Pack:
> https://www.reviewboard.org/powerpack/
> Want us to host Review Board for you? Check out RBCommons:
> https://rbcommons.com/
> Happy user? Let us know! https://www.reviewboard.org/users/
> ---
> You received this message because you are subscribed to the Google Groups
> "reviewboard" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to reviewboard+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
Supercharge your Review Board with Power Pack: 
https://www.reviewboard.org/powerpack/
Want us to host Review Board for you? Check out RBCommons: 
https://rbcommons.com/
Happy user? Let us know! https://www.reviewboard.org/users/
--- 
You received this message because you are subscribed to the Google Groups 
"reviewboard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to