Nice, that makes much more sense.

Guy

On Jul 25, 2014, at 2:28 PM, Christian Hammond <christ...@beanbaginc.com> wrote:

> Hi,
> 
> The login and password is just used the first time to fetch a token. We never 
> store those credentials. Instead, we pass them directly to the GitHub 
> Enterprise API and store the resulting token. That token will last until you 
> revoke it on GitHub Enterprise.
> 
> We're working on a full redesign of the repository page for a future release, 
> which will make this more clear and cause a token to be fetched client-side, 
> causing the username/password to never even go through our APIs.
> 
> Christian
> 
> -- 
> Christian Hammond - christ...@beanbaginc.com
> Review Board - http://www.reviewboard.org
> Beanbag, Inc. - http://www.beanbaginc.com
> 
> On July 25, 2014 at 2:26:07 PM, Guy Gascoigne-Piggford 
> (guy.piggf...@gmail.com) wrote:
> 
>> I've been evaluating the powerpack.  Is there a way to have the GitHub 
>> Enterprise repository hosting to use token based authentication rather than 
>> a user and password?  We enforce password aging (sadly) and I don't fancy 
>> having to fix the same duplicated account on every repo every 90 days.
>> 
>> For that matter it would be nice to be able to share the authentication 
>> information and not have it duplicated at all.
>> 
>> Guy
>> 
>> On Saturday, July 12, 2014 5:16:37 PM UTC-7, Christian Hammond wrote:
>> The issue is the way they handle authentication and access control. It used 
>> to be that a raw URL worked fine, but due to changes made in their API, it's 
>> no longer useable. For the data we need, in a way that works reliably, we 
>> have to use their API.
>> 
>> Christian
>> 
>> -- 
>> Christian Hammond - chri...@beanbaginc.com
>> Review Board - http://www.reviewboard.org
>> Beanbag, Inc. - http://www.beanbaginc.com
>> 
>> On July 12, 2014 at 5:11:23 PM, Guy Gascoigne-Piggford (guy.pi...@gmail.com) 
>> wrote:
>> 
>>> is the issue the https part of the raw url mask?
>>> 
>>> 
>>> On Saturday, July 12, 2014 4:55:20 PM UTC-7, Christian Hammond wrote:
>>> Git has no ability to fetch files remotely via the protocol, which is why 
>>> the raw URL mask is used. However, this is only useful for certain 
>>> services, and GitHub Enterprise is not one of them.
>>> 
>>> We provide official support for GitHub Enterprise as part of Power Pack, 
>>> which also offers PDF document review and, soon, reporting functionality. 
>>> This is at https://www.reviewboard.org/powerpack/.
>>> 
>>> You would need to set up a trial license or purchase a full license for 
>>> your server. Then, using GitHub Enterprise is as simple as adding a new 
>>> repository, choosing GitHub Enterprise as the hosting service, and 
>>> providing the details on which repository you want to add.
>>> 
>>> Christian
>>> 
>>> -- 
>>> Christian Hammond - chri...@beanbaginc.com
>>> Review Board - http://www.reviewboard.org
>>> Beanbag, Inc. - http://www.beanbaginc.com
>>> 
>>> On July 12, 2014 at 4:52:54 PM, Guy Gascoigne-Piggford 
>>> (guy.pi...@gmail.com) wrote:
>>> 
>>>> We're beginning the switch over to a locally hosted Github Enterprise from 
>>>> bzr and I'm looking at configuring reviewboard to work with git.  I've 
>>>> tried all sorts of permutations of the git repository settings but never 
>>>> get past a rather bland permission denied error.  Is there any way to get 
>>>> more details about what's broken?
>>>> 
>>>> Using reviewboard 1.7.25
>>>> 
>>>> I've enabled debug logging in admin UI, but all I ever see are lines like:
>>>> 
>>>> 2014-07-12 23:30:38,023 - DEBUG -  - GitTool: Attempting ssh connection 
>>>> with host: github.hostname.com, username: git
>>>> 
>>>> with no further details, no idea as to whether this worked or failed.
>>>> 
>>>> My repository configuration is:
>>>> 
>>>> repository type: Git
>>>> path: g...@github.hidden.com:ggp/testProject.git
>>>> mirrorPath: <blank>
>>>> raw file mask: 
>>>> https://github.hidden.com/ggp/testProject/raw/<revision>/<filename>
>>>> username: <blank>
>>>> password: <blank>
>>>> 
>>>> I've tried innumerable permutations of this, most of them seeming to have 
>>>> zero effect.
>>>> 
>>>> I have an ssh key installed, it appears to be correctly readable.  It does 
>>>> match one that's installed in our github.
>>>> 
>>>> The web server is running as user apache (on a Centos box), as apache I've 
>>>> been able to run:
>>>> 
>>>> ssh -vT g...@github.hidden.com  which is successful.
>>>> 
>>>> and:
>>>> 
>>>> DEBUG_RBSSH=1 rbssh g...@github.hidden.com
>>>> 
>>>> Which I think is successful.  It outputs an exception because the Channel 
>>>> is closed, but the rbssh*.log file says that authentication was successful.
>>>> 
>>>> 07-12 16:44 paramiko.transport DEBUG    userauth is OK
>>>> 07-12 16:44 paramiko.transport INFO     Authentication (publickey) 
>>>> successful!
>>>> 07-12 16:44 paramiko.transport DEBUG    [chan 1] Max packet in: 34816 bytes
>>>> 07-12 16:44 paramiko.transport DEBUG    Debug msg: Forced command.
>>>> 07-12 16:44 paramiko.transport DEBUG    Debug msg: Port forwarding 
>>>> disabled.
>>>> 07-12 16:44 paramiko.transport DEBUG    Debug msg: X11 forwarding disabled.
>>>> 07-12 16:44 paramiko.transport DEBUG    Debug msg: Agent forwarding 
>>>> disabled.
>>>> 07-12 16:44 paramiko.transport DEBUG    Debug msg: Pty allocation disabled.
>>>> 07-12 16:44 paramiko.transport DEBUG    [chan 1] Max packet out: 32768 
>>>> bytes
>>>> 07-12 16:44 paramiko.transport INFO     Secsh channel 1 opened.
>>>> 07-12 16:44 root               DEBUG    !!! Using PosixHandler
>>>> 07-12 16:44 root               DEBUG    !!! Opening shell
>>>> 07-12 16:44 paramiko.transport DEBUG    [chan 1] EOF sent (1)
>>>> 
>>>> /var/log/httpd/error_log isn't any more informative.
>>>> 
>>>> I'm missing something, can someone point me in the right direction please?
>>>> 
>>>> Thanks - Guy
>>>> 
>>>> --
>>>> Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/
>>>> ---
>>>> Sign up for Review Board hosting at RBCommons: https://rbcommons.com/
>>>> ---
>>>> Happy user? Let us know at http://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.
>>> --
>>> Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/
>>> ---
>>> Sign up for Review Board hosting at RBCommons: https://rbcommons.com/
>>> ---
>>> Happy user? Let us know at http://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.
>> --
>> Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/
>> ---
>> Sign up for Review Board hosting at RBCommons: https://rbcommons.com/
>> ---
>> Happy user? Let us know at http://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.

-- 
Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/
---
Sign up for Review Board hosting at RBCommons: https://rbcommons.com/
---
Happy user? Let us know at http://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