I want to setup a gitlab instance for internal use. Since the instance can only be reached over a local network I haven't setup the email setup. Unfortunately gitlab still wants to sent new users confirmation emails with a temporary password, but they never receive this email.
Is there a way to configure gitlab so that it doesn't send these confirmation mails? I already tried to set email_enabled: false in gitlab.yml but it didn't work.
Update:
It should work without me having to interfere manually in the signup process.
Admin can confirm user manually!
Login gitlab with admin account and create a new user (Mini), ignore password.
Admin area ---> users ---> edit Mini user ---> set password.
User Mini can login gitlab.
I think GitLab takes security seriously and from what I have seen so far, it looks like either your users need to confirm their accounts or an admin has to confirm manually.
Related
I wanted to change my username on GitLab so I followed the following procedure:
Navigate to your profile's Settings > Account.
Enter a new username under Change username.
Click Update username.
After clicking on update nothing seem to change so I refreshed the page and I receive the following error:
Your account has been blocked. Please contact your GitLab administrator if you think this is an error.
How do I unblock my account?
PS: I opened a GitLab SaaS account
This thread mentions
Check <external_url>/admin/application_settings/general > expand Sign-up Restrictions, and verify if the checkbox for Send confirmation email on sign-up is checked or unchecked?
Having that setting enabled will send a confirmation email, and for that user to be “unlocked”, it requires the confirmation link in the confirmation email is clicked.
If you’re creating a user with Ansible and the confirmation email isn’t received and the link it contains clicked, it would cause the “user is blocked” error you’re seeing.
If you did not check the box for this requirement, I suspect the default setting might’ve changed in 12.9.x. Do you notice if this checkbox was checked before upgrading?
Unchecking the box, or manually “confirming” the email of your Ansible-created user in the GitLab Admin UI should remove the block on this user.
In your case, since you are changing the user manually, see if:
the IP is blocked (try from another network/device)
if you have an IDE opened with a GitLab repository accessed through HTTPS: the IDE might need to refresh the Git repository state periodically, and would be using the old credentials (old username).
The OP goutam thakur confirms in the comments:
My account was unblocked after I submitted a request through the form "Gitlab.com (SaaS) user accounts and login issues".
I'm in a bind with Azure login account. I've forgotten my password for my account that I use for a client's DevOps. It wasn't until I ended up created another account today to troubleshoot the problem that I might understand the issue, but still can't fix it.
About a year ago, my client added me as a Guest in their Active Directory. I did not have an active directory myself. I got the notice from Microsoft in an invite email to get started, which created an account to get access to their Azure Portal and DevOps. I've been logged in for a year, but was trying test a feature which required me to login to DevOps during the process. I tried what I thought was my password, but that didn't work. No problem, I'll just click on the reset password feature. That ended up informing me that "password reset isn't properly set up for your organization." Knowing who setup my account up, I ask them to reset my password. The response was we do not have control to reset your password because you're a guest.
Through several discussions, and seeing what was available to them, and how a Guest was set up, it was suggested to setup an account within Microsoft for the email. I did that, and when I went back to try and login to their portal, I was presented with two options after I entered my email address. There was a work account and a personal account. Both with the same email address. The work account indicated it was created by "your IT department". Which we did not create this, it was a result of the client adding us as a guest, then finishing the process to gain access. So I can only assume, either an active directory was created for my domain, or I was added to a generic active directory.
In either case, I still can't change the password for the work account, and researching has not helped, as it keeps resetting my personal account.
Does anyone have any suggestions on how to resolve this issue?
Here is what I'm currently seeing.
Thank you,
Marc
You don't have an AAD tenant. So I assume that your account is an Microsoft personal account.
Although you are added as the guest user in your client's tenant, the password management is not handled by that tenant. It is still handled by Microsoft personal account.
You can reset your password here: click on Sign In, enter your account and click on Forgot password?.
I'm using gitlab 7.4.3
I want to create a user to sync a git repo with gitlab periodically. It's actually a git-svn checkout of a svn tree, so I plan to in cron run 'git svn fetch' and 'git push gitlab' every few minutes.
But I don't want this actively to show up as my activity. So I want to create a user, something like 'svnbot', and do the pushing as that user.
My problem is that I cannot create a user because I already have a user, and gitlab is requiring email addresses to be unique.
Ideally the user would have the same email as my account, so that any email it would receive goes to me. Also, having no email address at all would also be fine for my purposes. I don't want the email to leave the local domain, so I can't just put in a gmail account, and my email server doesn't support the "+" trick.
I have admin rights to the gitlab server, but not to the email servers, and I would prefer to not have to bother the email admins with this problem.
I'm guessing you need to contact your email admins. You can almost certainly get by with having them create an alias for your email account, e.g. 'gitlab-svn-bot#example.com'.
I'm having some trouble getting my mail setup to work with Gitlab 6 so I want the users to be able to sign up for an account and assign their own password instead of receiving the temporary password by mail.
Changes I've made:
/home/git/gitlab/config/gitlab.yml:
`signup_enabled: true`
But if I access Gitlab in the Browser it's still redirecting me to the "Sign in" page and I'm not able to "Sign up" or register a new account. Is there something I'm missing?
Thanks!
You have to restart the GitLab server after making that change.
I've setup Jenkins, and it's working well. It uses the Perforce plugin as the SCM, and builds automatically upon a checkin. My issue is that when a user makes a commit to the tree it auto creates a user account on the system, but no password is set, and the user cannot login.
The system is secured on a intranet, and I have set Jenkins to use "Jenkins own user database" and "Logged in users can do anything". Problem is I can't find any way for someone to log in once they have made a commit, there username is shown in the list of auto-created accounts, but no password is ever sent. Is there a default password, or a way to reset?
The system is running on Ubuntu 12 with Tomcat7 serving the Jenkins front end.
Users created by SCM are not "full" users. They are created for purposes of showing SCM changes and receiving e-mails. Therefore they need to sign up (using 'Sign Up' icon that appears to the left of of 'log in' icon in the upper right corner) and provide their password. It is advisable for the username to match the SCM name.
Alternatively, a user with a "full" account can go to http://<jenkins-server>/people/ -> click on username -> click on Configure link to the left, and configure the user (I'm not 100% sure if this will work, though, try it).
With version 1.517, signing up didn't work and gave the "User name is already taken" error.
However you can go to to http://<jenkins-server>/user/<autogenerated username>/configure and set a password for the SCM user, which converts them into a full Jenkins user.
Go to `Manage Jenkins -> scroll down
click on "Manage User" -> see userId -> click on setting symbol right side of user id(admin)->change the password field->click on save.
Now you can login with new credentials