Can we desactivated OpenID login?

144 views
Skip to first unread message

Dominick Rivard

unread,
Aug 9, 2012, 11:45:16 PM8/9/12
to gito...@googlegroups.com
Hi,

I installed my gitorious on a shared hosting (my only public server I have access too) and I want to deactivate the openid login.
I don't see any link to register that is good because it is my personal repository and no one should access it other than me.
But I still see the openid login. Is there a way to disable it through a configuration?

Thank you!
Dominick

Ken Dreyer

unread,
Aug 10, 2012, 1:32:33 AM8/10/12
to gito...@googlegroups.com
On Thu, Aug 9, 2012 at 9:45 PM, Dominick Rivard
<dominic...@gmail.com> wrote:
> Is there a way to disable it through a
> configuration?

The functionality does not yet exist in mainline gitorious, but there
is a patch in the merge request queue to do this [1]. If the patch
works for you, you could offer some positive feedback in the merge
request, and the gitorious devs might be more inclined to merge it in
:)

- Ken

[1] https://gitorious.org/gitorious/mainline/merge_requests/2247

Thomas Kjeldahl Nilsson

unread,
Aug 10, 2012, 3:03:20 AM8/10/12
to gito...@googlegroups.com
Hello,

Just a quick note from the devs end: we have been stretched thin for a
while but are now finally able to step up the effort again.
I'm starting a cleanup in the MR backlog next week, will prioritize this
then.
The idea is to be a lot more responsive on Gitorious merge requests this
fall. :)

cheers,
Thomas
--
best regards,
Thomas Kjeldahl Nilsson
http://gitorious.com

Dominick Rivard

unread,
Aug 10, 2012, 1:57:27 PM8/10/12
to gito...@googlegroups.com, tho...@gitorious.com
I would be happy to help out. I just need to find out how to get that specific patch from git.

Thank you!
Dominick

Ken Dreyer

unread,
Aug 10, 2012, 2:17:07 PM8/10/12
to gito...@googlegroups.com, tho...@gitorious.com
On Fri, Aug 10, 2012 at 11:57 AM, Dominick Rivard
<dominic...@gmail.com> wrote:
> I would be happy to help out. I just need to find out how to get that
> specific patch from git.

Sure, visit this link:
https://gitorious.org/gitorious/mainline/merge_requests/2247

Then click the "How to apply this merge request to your repository"
link in the blue box. There's a list of instructions there.

You don't have to follow the final section labeled "# To apply the
changes to your branch:", since you don't have a public Gitorious
clone. After you've got your patch into your local Gitorious
installation, you can test it out. Set "enable_openid" to false in
your gitorious.yml configuration, preferably just below the
"enable_private_repositories" setting.

enable_openid: false

- Ken

Dominick Rivard

unread,
Aug 15, 2012, 11:18:55 AM8/15/12
to gito...@googlegroups.com, tho...@gitorious.com
Hi Ken,

Thanks for pointing out the instructions. I followed them, the only thing I added to fix was a conflict in the gitorious.sample.yml. 
After that I modified my gitorious.yml with:

enable_openid = false

I restarted the passenger with touch public/restart.txt and it is working. No more Open ID on the login prompt.

Thank you for your great help.
Dominick

Ken Dreyer

unread,
Aug 26, 2012, 5:58:01 PM8/26/12
to gito...@googlegroups.com, tho...@gitorious.com
On Wed, Aug 15, 2012 at 9:18 AM, Dominick Rivard
<dominic...@gmail.com> wrote:
> Thanks for pointing out the instructions. I followed them, the only thing I
> added to fix was a conflict in the gitorious.sample.yml.

Ok, sounds like the author needs to rebase their merge request onto
the latest version of the code in mainline. I added a comment to the
merge request.

> I restarted the passenger with touch public/restart.txt and it is working.
> No more Open ID on the login prompt.

That is great! Can you please leave feedback in the merge request and
say that this feature works for you? You can just say something like
"+1, tested and working here." That way, the core Gitorious developers
can have more information when they decide to merge the patch into
mainline. The more eyeballs that do code reviews, the better.

- Ken
Reply all
Reply to author
Forward
0 new messages