Currently, All our team members are using same username & password to login Jenkins. Is there a way, which allows Jenkins login using VS TFS login credentials for each members separately.
Any help would be appreciated.
Login Jenkins as admin->Jenkins->Manage Jenkins-> Configure Global Security->enable the feature Logged-in users can do anything
Manage Jenkins->Manage User->Create User->enter username and password with TFS credentials->click the button Create User
Then you could login Jenkins with TFS credentials.
Update1
Add domain and credentials usable to connect to your TFS server via Jenkins > Configure Credentials.
Now select just added domain, click "Configure", and add your TFS server hostname (or proper wildcard) under Hostname > Include, so jenkins will know where provided credentials can be used.
Now, you can just leave user/password fields empty in job's TFS SCM configuration.
Instructions are mostly taken from TFS plugin GitHub page
Related
WAS is configured to use an Active Directory to authenticate, but the default admin account was left on the local file repository. When the AD connection is working we are able to login to the admin console using the default admin account, but when AD is down we are not able to use the default admin account to login. Any ideas as to why this is happening?
Any help would be greatly appreciated.
Check this link Unable to authenticate when a repository is down. You didnt write which version you are running, but by default if one of the federated repos is down you will not be able to log in.
You can use updateIdMgrRealm wsadmin command to set the –allowOperationIfReposDown parameter to true. This will allow you to log in with the user from working repository.
I've installed the LDAP Integration plugin in SonarQube(Version 5.4) and restarted the server.
I didn't make any changes to config file.
When I try to login, a credential prompt pops up, here I enter the same credentials I use to login to server. But even after this the sonarqube console asks me for a username and a password, this is the sonarqube username and password not the windows one's.
Do I need to make any changes for SonaQube to use windows credentials? or is it just ldap?
Please let me know if I'm missing something here.
I'm using Vs2013 and TFS for my project.
I have to run my VS in admin mode because of some reason but it ask me TFS credential every time when i start vs.
I'm tired of being provide it every time.
Is there any workaround so that TFS will connect automatically without asking credential every time.
Note: I logged as Normal user and running VS in admin mode by using "Run as".
If you log into your local machine with the same credentials as you are trying to connect to TFS you will get automatic ostrich with active directory. The fact that it is asking for credentials at all is unusual in an active directory configuration. If you are logging into another domain with credentials that are not the same as your local ones then use the windows credential store to save the credentials for the TFS server name or domain name.
I'm currently 'playing' with Plastic and their (brand new) TeamCity integration plugin.
The plugin blurb says "When installing Team City on Windows systems, it normally uses the SYSTEM user account. We recommend changing the user that executes the Team City application."
The thing is, I can't work out what kind of user I should substitute: I would like to be able to access Plastic (on the server) using AD, but wouldn't that mean that TeamCity would also have to run with a network user in order to be able to access Plastic?
An alternative (for me accessing Plastic) would be user/password - but I can't make the TeamCity service run with user/password.
Am I missing something obvious, or is the paint just too wet?
I'm also using PlasticSCM and the Team city plugin, this is my configuration:
For the server: configure your PlasticSCM server with LDAP authentification and select "Active Directory" as the server type.
For the client: configure your PlasticSCM client with LDAP authentification, use your credentials and try the "Test connection" button.
The client setup will generate a "client.conf" file at "C:\Users\your_user\AppData\Local\plastic". This file is used by PlasticSCM client to authenticate with the PlasticSCM server.
So, if your TeamCity service is running with the administrator account you have to place this file in your Administrator "...\AppData\Local\plastic" directory. If you change your TeamCity service to be run with your system account you don't need to do anything, the file is in the right place.
You have another option (if you are still running the TeamCity plugin as Admin), place the "client.conf" file where your "cm.exe" file is. Because the "cm.exe" is going to try to find this file first on its own location and then in the current user "AppData\Local\plastic" directory. This option is only valid if you are the only user working with PlasticSCM in the machine.
Hope it helps!
Just installed teamcity 6.5.6 after uninstalling 6.5.4 after trying to implement a svn 1.7 plugin that seemed to have buggered up my TC configurations.
Trying to revert back to working times so I did a fresh install of the latest release.
I created my initial admin user with the same credential I have for the admin user on the server machine that is running TC.
Once I change the config to NTLM auth, I login as the same user, and that user no longer has admin privileges. Any ideas why?
The documentation states that:
Please note that each authentication type maintains own list for users. This means that on switching from one authentication to another you start with no users (and no administrator) and will be prompted for administrator account on first TeamCity start after the authentication change. This also means that all the existing users will need to create their accounts and re-enter their settings anew.
So when you switched to NLTM authentication you will have be prompted to specify the admin user again.
http://confluence.jetbrains.net/display/TCD65/Configuring+Authentication+Settings