Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Message from discussion Can we desactivated OpenID login?

Date: Wed, 15 Aug 2012 08:18:55 -0700 (PDT)
From: Dominick Rivard <dominick.riv...@gmail.com>
To: gitorious@googlegroups.com
Cc: tho...@gitorious.com
Message-Id: <c66ea7a9-ad09-486d-8679-7d3e122b0b67@googlegroups.com>
In-Reply-To: <CAD3FbMVvRkZ0yNqd3A8Jvf7ajix31VjHQX4zeyeD_rVsMU0vkQ@mail.gmail.com>
References: <167b8ba8-abd6-4ed3-b62c-9a9d81c50a01@googlegroups.com>
 <CAD3FbMUL=E=naE0ZfEKnXm=_tqunwzkLf2YNSQZyoSjzHwDjSA@mail.gmail.com>
 <5024B238.9080408@gitorious.com>
 <64b37e73-f0d8-4099-b5a5-9837692c42a0@googlegroups.com>
 <CAD3FbMVvRkZ0yNqd3A8Jvf7ajix31VjHQX4zeyeD_rVsMU0vkQ@mail.gmail.com>
Subject: Re: [gitorious] Can we desactivated OpenID login?
MIME-Version: 1.0
Content-Type: multipart/mixed; 
	boundary="----=_Part_1412_20793739.1345043936071"

------=_Part_1412_20793739.1345043936071
Content-Type: multipart/alternative; 
	boundary="----=_Part_1413_10970921.1345043936071"

------=_Part_1413_10970921.1345043936071
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

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


On Friday, August 10, 2012 2:17:07 PM UTC-4, Ken Dreyer wrote:
>
> On Fri, Aug 10, 2012 at 11:57 AM, Dominick Rivard 
> <dominic...@gmail.com <javascript:>> 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 
>

------=_Part_1413_10970921.1345043936071
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 7bit

Hi Ken,<div><br></div><div>Thanks for pointing out the instructions. I followed them, the only thing I added to fix was a conflict in the gitorious.sample.yml.&nbsp;</div><div>After that I modified my gitorious.yml with:</div><div><br></div><blockquote style="margin: 0 0 0 40px; border: none; padding: 0px;"><div>enable_openid = false</div></blockquote><div><br></div><div>I restarted the passenger with touch public/restart.txt and it is working. No more Open ID on the login prompt.<br></div><div><br></div><div>Thank you for your great help.</div><div>Dominick</div><div><br><br>On Friday, August 10, 2012 2:17:07 PM UTC-4, Ken Dreyer wrote:<blockquote class="gmail_quote" style="margin: 0;margin-left: 0.8ex;border-left: 1px #ccc solid;padding-left: 1ex;">On Fri, Aug 10, 2012 at 11:57 AM, Dominick Rivard
<br>&lt;<a href="javascript:" target="_blank" gdf-obfuscated-mailto="3Ohaqi7a5n4J">dominic...@gmail.com</a>&gt; wrote:
<br>&gt; I would be happy to help out. I just need to find out how to get that
<br>&gt; specific patch from git.
<br>
<br>Sure, visit this link:
<br><a href="https://gitorious.org/gitorious/mainline/merge_requests/2247" target="_blank">https://gitorious.org/<wbr>gitorious/mainline/merge_<wbr>requests/2247</a>
<br>
<br>Then click the "How to apply this merge request to your repository"
<br>link in the blue box. There's a list of instructions there.
<br>
<br>You don't have to follow the final section labeled "# To apply the
<br>changes to your branch:", since you don't have a public Gitorious
<br>clone. After you've got your patch into your local Gitorious
<br>installation, you can test it out. Set "enable_openid" to false in
<br>your gitorious.yml configuration, preferably just below the
<br>"enable_private_repositories" setting.
<br>
<br>&nbsp; enable_openid: false
<br>
<br>- Ken
<br></blockquote></div>
------=_Part_1413_10970921.1345043936071--

------=_Part_1412_20793739.1345043936071--