Connecting to repositories

A repository is a central location to store data. You must create a connection from Visual Studio to a repository in Jazz™ to work with the project artifacts. Your Jazz Team Server administrator must provide you with the access privilege to the repository.

Before you begin

This topic assumes that your Jazz Team Server administrator has created a repository and a project area.

To connect to a repository, you need the following information:
  • The Uniform Resource Identifier (URI) of an existing repository. Typically, this is in the form of https://<>:<port>/ccm. The repository is created by a Jazz Team Server administrator. The repository must be available on a local or a network server.
  • A user ID and password for the repository. Jazz Team Server administrators create team member credentials on the Web server and in team areas. Your administrator can configure the repository for user authentication in an LDAP directory.

To use Smart Card authentication, you must enable the IBM Common Access Card (CAC) provider within Java by editing the install-directory/3rd Party/jre/lib/security/ file.

Replace this section:
with this section:

After creating a repository connection, you can connect to that repository.


  1. In Microsoft Visual Studio, click Team Concert > Windows > Team Artifacts.
  2. In the Team Artifacts tool window, right-click Repository Connections and click New > Jazz Repository Connection.
  3. In New Repository Connection window, type or paste a URL. For example, The Name defaults to the server host name. You can modify the name.
  4. Type the user name and password that your Jazz Team Server administrator provided for you.
  5. Optional: To authenticate using Kerberos/SPNEGO, complete the following steps:
    1. In the Authentication Type field, select Kerberos/SPNEGO. If the client is configured with krb5.ini or krb5.conf in a default location, click Finish. Otherwise, set additional configuration options.
    2. To specify a Kerberos configuration file, expand Additional configuration options. In the Kerberos configuration file field, browse to the location of the file. The file can have any name.
    3. To specify a Kerberos realm name, host, and (optional) key distribution center port, complete the appropriate configuration fields.
    4. Click Finish.
    Note: The Kerberos realm, Key distribution center, and Kerberos configuration file properties map to the,, and system properties, respectively. For more information, see Jazz client configuration. The configuration option properties are global for your client, so if you have multiple repository connections, these properties are automatically shared. Changing the properties in one connection automatically changes them in any other Kerberos/SPNEGO connection. To apply a change to a configuration option that is already set, restart the client.
  6. Optional: To log in using Windows credentials that are the same as the credentials that you use to access the CCM application, in the authentication field select Integrated Windows Authentication.
    Note: You must be logged in to a workstation and authenticated by domain. You can use this authentication method instead of Kerberos/SPNEGO authentication if the Windows registry on a client machine does not have the required AllowTGTSessionKey=1 key. For more information about the AllowTGTSessionKey, see Providing a session key to the IBM JRE to enable Kerberos/SPNEGO SSO in CLM.
  7. Click OK. The repository connection is displayed in the Repository Connections folder of the Team Artifacts tool window.
  8. To connect to the repository, right-click the repository connection and click Logon. You will be logged in automatically, if you selected Remember my password, while creating a repository connection. Otherwise, a dialog box is displayed prompting you to enter password. Type the password and click OK.

video icon Watch videos

CLM playlist channel
User Education channel

learn icon Learn more

CLM learning circle
Agile learning circle
Learning circles

ask icon Ask questions forum
developerWorks forums

support icon Get support

Support Portal
Deployment wiki
Support blog