[Girder-users] Setting up proxied Girder with Docker Container

[Zach Mullen]

That is, what is the value listed in your OAuth application's *Authorization
callback URL* field, which looks like the below screenshot:

[image: Inline image 1]

On Thu, Feb 2, 2017 at 8:24 PM, Zach Mullen <zach.mullen at kitware.com> wrote:

> To diagnose that issue, how is your redirect URI configured in github? And
> what is the value of the "state" parameter when you are sent to the github
> login page?
>
>
>
> On Thu, Feb 2, 2017 at 8:07 PM, John Roberts <John.Roberts at hsc.utah.edu>
> wrote:
>
>> Thanks for the reply, Zach.
>>
>> Playing around with a test girder/mongo pair, I managed to edit the
>> girder.local.cfg file without crashing the container.  Subsequently, it
>> seems to recognize correctly that it is not at the top level of the web
>> server.
>>
>> This is all related to our effort to run oauth through github.
>> Previously, without the proper proxy settings in girder.local.cfg, the
>> callback address generated in the oath plugin setting did not include the
>> proxy.  Now it does.
>>
>> Unfortunately, authorization through github still generates a
>> redirect_uri_mismatch error.
>>
>> My best guess at the moment is that this is somehow related to our
>> proxying girder itself through https on the Apache server.  I mean, we have
>> a reverse proxy setup on Apache to route incoming requests for
>> https://some.address.com/girder to our internal
>> http://some.docker.network:8080/girder.
>>
>> Somewhere in the proxying, I'm thinking the URL might be modified and
>> either Girder or Github says it doesn't match what's expected.  The message
>> indicates that it's Github who is rejecting the callback:
>>
>> {
>>     "message": "Provider returned error: 'redirect_uri_mismatch'.",
>>     "type": "rest"
>> }
>>
>>
>> John.
>>
>> On 02/02/2017 05:06 PM, Zach Mullen wrote:
>>
>> Hi John,
>>
>> You're running an old version of Girder (1.5.2), are you able to upgrade
>> to the latest version and see if that fixes the issue?
>>
>> Thanks,
>>
>> Zach Mullen
>> Kitware, Inc.
>> 919-869-8858 <(919)%20869-8858>
>>
>> On Thu, Feb 2, 2017 at 6:25 PM, John Roberts <John.Roberts at hsc.utah.edu>
>> wrote:
>>
>>>     I'd like to set up a proxied Girder as detailed in the manual here
>>> <https://girder.readthedocs.io/en/v1.5.2/deploy.html?highlight=root>.
>>> We need to configure girder so that it understands it is not working from
>>> the root directory of the Apache server but one directory down (/girder).
>>> Unlike the situation in the documentation, I'm working with the Docker
>>> girder.
>>>
>>>     If I rather blindly edit the girder.local.cfg file within the
>>> running container, the container crashes as soon as I save the file.  This
>>> may have been due to a typo, but I have a further question.
>>>
>>>     Assuming I did update girder.local.cfg properly as indicated, the
>>> instructions then say to rebuild Girder using "npm install".  It's my
>>> impression that this will likely crash the girder container itself, since
>>> the current girder process will likely be terminated while the new build is
>>> being compiled with npm.  Would that be a correct assumption?
>>>
>>>     The question is how to configure Girder within the container to
>>> invoke the proxy and move the address space one step down from root at / to
>>> a proxied address /girder.  A more general question might be how to update
>>> girder.local.cfg when running Girder with Docker.
>>>
>>>     I tried running the Docker girder:girder image and entering by way
>>> of an alternative entry-point,
>>>
>>> docker run -it --entrypoint=/bin/bash girder/girder -s
>>>
>>> This lets me in and I can edit the girder.local.cfg file.  However, "npm
>>> install" then appears to fail with the warning "cannot run in wd
>>> girder at 1.5.2 grunt init && grunt (wd=/girder)".  Since I don't know
>>> what "npm install" was supposed to accomplish, I'm not sure where to look
>>> to see if it succeeded despite the warning.
>>>
>>> Thanks for suggestions,
>>> John.
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> Girder-users mailing list
>>> Girder-users at public.kitware.com
>>> http://public.kitware.com/mailman/listinfo/girder-users
>>>
>>>
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/girder-users/attachments/20170202/cfe67add/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Screen Shot 2017-02-02 at 8.29.34 PM.png
Type: image/png
Size: 47687 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/girder-users/attachments/20170202/cfe67add/attachment-0001.png>