If you're using LDAP, won't the user's password be the LDAP password? Regards, Daniel Serodio
On Wednesday, January 28, 2015 at 2:53:07 PM UTC-2, Bram Daams wrote: > > Hi, > > I'm setting up a registration script that uses the gitlab API to create > gitlab user accounts. > > When I POST the request with the required parameters (email, name, > username, password), two mails are sent: > > ======== > Subject: Confirmation instructions > Body: > Welcome Your name here! > > You can confirm your account through the link below: > > Confirm my account[1] > ======== > > Followed by: > > ======== > Subject: Account was created for you > Body: > Hi Your name here! > > The Administrator created an account for you. Now you are a member of the > company GitLab application. > > login.......................................... john...@example.com > <javascript:> > > — > View it on GitLab[2] > ======== > > > When John Doe in this example, follows the first confirmation link, he'll > see a > flash message: > "Your account was successfully confirmed. You are now signed in."" > > From there, he can't change his password. Because he doesn't know his > password. > > To get John to work with gitlab. He should: > > - logout. > - Navigate to the standard login form (we have ldap enabled and that > login form is displayed on top) > - click "Forgot your password?" > - fill in his mail address > - check mail > - click the "Change my password" link in the mail. > - Then he can set his password. > > This is quite a contrast compared to an account created by an admin user: > > Hit the "New User" button in the user overview > > - fill in: name, username, email > - hit create user > - the user gets an email with subject: "Account was created for you" > - the mail contains a link set a password > > Ideally, you want to have the password field optional in the user create > api call. If the password is omitted, the newly create user should receive > just one mail, just like when done manually through the UI. > > Seems like a bug to me. All functionality seems to be thare, but it looks > like the wrong action is triggered. > Am I doing something wrong here? > Is there a work-around? > > Using the latest (7.7.1) omnibus install. > > Bests, > > Bram > -- 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 gitlabhq+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/gitlabhq/4f1954ea-9dac-46ba-8b88-cadcc0610425%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
