We're decrypting the value before plugging it into any requests. Running that same script but with decrypt_password (and specifying the stored token) will give you what we're passing on to the server in a request.
Christian -- Christian Hammond - christ...@beanbaginc.com Review Board - https://www.reviewboard.org Beanbag, Inc. - https://www.beanbaginc.com On Thu, Dec 17, 2015 at 1:41 AM, Ian <iander...@mac.com> wrote: > So close. That gave me a different token value from the original one, but > now I'm back to "A repository with this name was not found on this group, > or your user may not have access to it." > > Ian > > On Thursday, December 17, 2015 at 1:37:01 AM UTC-8, Christian Hammond > wrote: >> >> We store the token in an encrypted form, which is why you're getting that >> error. >> >> You can figure out the value to insert into there by doing: >> >> $ rb-site manage /path/to/site shell >> >>> from reviewboard.scmtools.crypto_utils import encrypt_password >> >>> print encrypt_password('<your token here>') >> >> That should give you the right value to paste in the box. >> >> Christian >> >> -- >> Christian Hammond - chri...@beanbaginc.com >> Review Board - https://www.reviewboard.org >> Beanbag, Inc. - https://www.beanbaginc.com >> >> On Thu, Dec 17, 2015 at 1:34 AM, Ian <iand...@mac.com> wrote: >> >>> Well, I got something. I went to the Hosting Account in Review Board's >>> admin UI and copied the private_token out of the Data box. Then I did this >>> one. >>> curl --header "PRIVATE-TOKEN: <copied token>" "https:// >>> <server>/api/v3/groups/<group>" >>> >>> That said >>> {"message":"401 Unauthorized"} >>> >>> Then I logged into the GitLab web page, went to Profile and then >>> Account. I saw that the private token there was completely different. I >>> tried that one with the curl command and then it worked fine and I could >>> see all my repositories/projects. (There's actually 7, one of them >>> is "archived":true and doesn't show up in the GitLab UI.) >>> >>> So I went back to Review Board and pasted the working private token into >>> the Hosting Account and saved that. But now when I try to save a >>> repository I get this error. >>> IV must be 16 bytes long >>> >>> Ian >>> >>> On Thursday, December 17, 2015 at 12:53:26 AM UTC-8, Christian Hammond >>> wrote: >>>> >>>> Hmm, okay. In that case, logged in as the user, can you try accessing: >>>> >>>> http://<server>/api/v3/groups/<groupname> >>>> >>>> See what that payload looks like, and if the repository you expect is >>>> in there anywhere. >>>> >>>> Christian >>>> >>>> -- >>>> Christian Hammond - chri...@beanbaginc.com >>>> Review Board - https://www.reviewboard.org >>>> Beanbag, Inc. - https://www.beanbaginc.com >>>> >>>> On Thu, Dec 17, 2015 at 12:50 AM, Ian <iand...@mac.com> wrote: >>>> >>>>> Oh sorry I thought you meant total repositories on the server. This >>>>> user only has access to 1 group and 6 repositories under that. >>>>> >>>>> Ian >>>>> >>>>> On Wednesday, December 16, 2015 at 11:58:45 PM UTC-8, Christian >>>>> Hammond wrote: >>>>>> >>>>>> Okay, this is likely the issue. The repositories can't be found >>>>>> because we couldn't sanely iterate before, and had to limit it to 100 >>>>>> repositories. >>>>>> >>>>>> A workaround (not a great one) is to have a user per 100 >>>>>> repositories, so that the pagination issue doesn't happen. >>>>>> >>>>>> Another is to temporarily modify the check_repository method in >>>>>> reviewboard/hostingsvcs/gitlab.py to return early, instead of attempting >>>>>> to >>>>>> look up the repository, so that you can save. >>>>>> >>>>>> I'll see what we can do for the next releases of Review Board. >>>>>> >>>>>> Christian >>>>>> >>>>>> -- >>>>>> Christian Hammond - chri...@beanbaginc.com >>>>>> Review Board - https://www.reviewboard.org >>>>>> Beanbag, Inc. - https://www.beanbaginc.com >>>>>> >>>>>> On Wed, Dec 16, 2015 at 11:51 PM, Ian <iand...@mac.com> wrote: >>>>>> >>>>>>> How many repositories total? Probably way (way) more than 100. But >>>>>>> I only have about 10 configured in Review Board. >>>>>>> >>>>>>> Ian >>>>>>> >>>>>>> On Wednesday, December 16, 2015 at 11:18:18 PM UTC-8, Christian >>>>>>> Hammond wrote: >>>>>>>> >>>>>>>> Hi Ian, >>>>>>>> >>>>>>>> There's a few possible APIs that it may call, but I realized what >>>>>>>> could potentially be the issue... >>>>>>>> >>>>>>>> How many repositories do you have on the server? Due to limitations >>>>>>>> that used to exist (hopefully don't anymore) with the GitLab API, we >>>>>>>> weren't able to fetch more than 100 entries very cleanly, and our code >>>>>>>> is >>>>>>>> still adhering to that limitation. >>>>>>>> >>>>>>>> Christian >>>>>>>> >>>>>>>> -- >>>>>>>> Christian Hammond - chri...@beanbaginc.com >>>>>>>> Review Board - https://www.reviewboard.org >>>>>>>> Beanbag, Inc. - https://www.beanbaginc.com >>>>>>>> >>>>>>>> On Wed, Dec 16, 2015 at 6:46 PM, Ian <iand...@mac.com> wrote: >>>>>>>> >>>>>>>>> It worked far enough to re-link, I got a new private_token for the >>>>>>>>> new temporary hosting account. But I still get the same error every >>>>>>>>> time I >>>>>>>>> try to save any of my repositories. Is there a particular URL that >>>>>>>>> Review >>>>>>>>> Board builds based on the repository information I entered that I >>>>>>>>> could >>>>>>>>> test in a web browser? >>>>>>>>> >>>>>>>>> Ian >>>>>>>>> >>>>>>>>> On Wednesday, December 16, 2015 at 12:00:54 PM UTC-8, Christian >>>>>>>>> Hammond wrote: >>>>>>>>>> >>>>>>>>>> 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 - chri...@beanbaginc.com >>>>>>>>>> Review Board - https://www.reviewboard.org >>>>>>>>>> Beanbag, Inc. - https://www.beanbaginc.com >>>>>>>>>> >>>>>>>>>> On Tue, Dec 15, 2015 at 9:00 PM, Ian <iand...@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...@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...@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...@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.
