Just in case someone else runs into the same problem, that's a bug
in the Gitlab version 7.6.x and previous. It has been fixed in
commit 058f223b.
Cheers,
Sergio Oliveira
On Wednesday, January 7, 2015 at 11:44:46 AM UTC-2, simon farrow wrote:
>
> I'm running gitlab inside a docker container. I've configured the
> parameters to enable github authentication.
>
> When I get bounced back from github to the gitlab server I get a 500 error
>
> The production.log contains
>
> rocessing by OmniauthCallbacksController#github as HTML
> Parameters: {"code"=>"b3d58aa369d01e8c71d1",
> "state"=>"2aa509baa11bde54fda29b2f53ab17361bfe826f6b32c194"}
> Completed 500 Internal Server Error in 8ms
>
> NameError (uninitialized constant
> OmniauthCallbacksController::ForbiddenAction):
> app/controllers/omniauth_callbacks_controller.rb:68:in `rescue in
> handle_omniauth'
> app/controllers/omniauth_callbacks_controller.rb:44:in `handle_omniauth'
> app/controllers/omniauth_callbacks_controller.rb:4:in `block (2 levels)
> in <class:OmniauthCallbacksController>'
>
> I'm pretty much stumped at this point.
>
> Thanks,
>
> Simon.
>
--
You received this message because you are subscribed to the Google Groups
"GitLab" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/gitlabhq/964671e5-1d21-4aea-bb65-893dca8a9aad%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
