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
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".
How to reset GitLab user password of a normal user via UI ?
(Via command line it is possible using rake)
We are using an on-premise GitLab community edition
To change/reset your own GitLab user password: see change your password
As a GitLab administrator, to (re)set another user's password in the UI:
Navigate to Admin Area -> Users
Locate the user whose password you want to reset
Click "edit"
Enter new password (and again in confirmation field)
Click "save"
As you mentioned, you can also use a rake task or rails console.
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.
I am trying to sort out a peculiar behavior when creating new users as a site Admin on our Dnn installation.
I have gone into the Admin > Site Settings > User Account Settings > Profile Settings and changed a few of the fields to Required (FirstName, LastName, Title, Address etc) with Required and Visible checked and Default Visibility set to 'AllUsers'.
I have a requirement of 'None' for the 'User Registration' type, meaning the site Admin must create all new users. I also have a requirement that the password for new users be created randomly, instead of being assigned by the site Admin.
When the user is created in this manner, an email is sent with instructions to choose the 'Reset Password' option (if first time user). This built in Dnn function asks for the new user name (supplied in the email) and then sends another email with a reset password link with a token.
We are doing this to remove any password knowledge from the site Admin.
The problem is that when new users finally set their password and gain access to the system they are not being forced to fill in the required profile settings the first time (when they choose their password). They are required to fill them out when they log in the second time (without going through the reset password process).
We would really like them to be forced to complete the Profile Settings the first time regardless of whether they are setting their password via the password reset token link.
Does anyone know why this is happening? Is there a workaround?
Thanks for any information!
The answer to this question can be found here:
https://dnntracker.atlassian.net/browse/DNN-4213
Every morning when i fire up my VM and IE (in my host OS) and go to my SP site it always logs me on automatically as DOMAIN\george which is a user I created for testing permissions.
So every morning after that I click "sign in as a different user" to sign in as my sys admin user instead and most days that is the only user I use. Any idea why george's credentials are being cached?
Part of "firing up my VM" is running a script that starts IIS as well as some services. I'm not entirely sure SharePoint is responsible for this, could very well be ASP.Net.
EDIT: I've already tried clearing my cookies.
Had a very similar problem! To solve it, go to 'User Accounts' under the Windows Control panel.
Navigate to 'Manage your network passwords'. Select the domain you wish to clear and select 'Remove'.
You should now have a clean login dialogue box and when you check the 'remember me' box, this will be stored as the login default for that domain.
I was able to remove the test login credentials using the User Account control panel applet in Windows 7
Open the Manage Credentials link.
Find the Sharepoint Login in the Windows Vault.
Expand the address for the site
Remove the test login for this site.
After doing this I am no longer prompted for the login and login as different user prompt.
Have you checked that there are no logins and passwords being stored by the browser? Assuming you are using IE, see this article on how to clear them.
If DOMAIN\george is same user ID you are logging in to the VM ? If that is the case try changing the Setting in IE that dictates what user name is send to the Server. Just go to Tools - > Settings - > Security and Click on Custom Level, scroll down to bottom and you will find User Authentication option Select the Prompt for User name and Password.
It could also be that you are using IE8, that caches my credentials as well it seems.
IE8 stores credentials for favourites it seems, don't ask me why. What you should do is log in as the needed user, then save a new favourite (or add it to the favourites bar by dragging it). Then use that link to go to your site.