Ok, I found that 
this<https://github.com/criteo/gitlabhq/commit/2c4e3e001f2e3b22546d9a0288ca7d2d7121fff1>
 commit 
fix the issue about the confirmation e-mail, which should not be sent when 
logging through an omniauth provider.

The only problem now is about the random password that is created when 
logging with a kerberos user for the first time, never sent to the user, 
and asked by gitlab when cloning a repository. What I'd expect from gitlab 
is to ask the kerberos password when cloning a repository, not the random 
generated one.

Em segunda-feira, 6 de janeiro de 2014 11h20min03s UTC-2, Diego Pasqualin 
escreveu:
>
> Hi, I'm facing a problem here with omniauth login (kerberos).
>
> I have the allow_single_sign_on option set to "true", which means an user 
> account is created on gitlab when the user logs in for the first time using 
> kerberos.
>
> The authentication is working and the user account is successfully 
> created. The problem is that I was expecting to be able to clone 
> repositories using the kerberos login+password, but gitlab creates a 
> different (random) password for the user, which is never send or can be 
> known by the user. The only thing I get on the account confirmation e-mail 
> sent by gitlab is the following:
>
> ----------------8<-------------------------------------------------
>
> Welcome [email protected]!
>
> You can confirm your account through the link below:
>
> Confirm my account
>
> ----------------8<-------------------------------------------------
>
> If I click in "Confirm my account" I get the following page:
>
> In this page, if I add my e-mail and click in "Resend.." I get the 
> following message: "Email was already confirmed, please try signing in"
>
>
>
> <https://lh4.googleusercontent.com/-80k4AFSTzIk/UsqstfEAHrI/AAAAAAAAAJY/6VWNmTOFQsU/s1600/download.jpg>
>
> Any thoughts on that?
>
>

-- 
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].
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to