Connecting to repositories and project areas

Users must create a connection from the client to a repository for access to project areas. Your Jazz administrator must supply information to enable your access to the repository.

Before you begin

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

You need the following information to connect to a repository:
  • The Uniform Resource Identifier (URI) for an existing repository. Typically, this address is in the form of http://hostname.example.com:9443/ccm, where you must substitute your own fully qualified host name and port number. Secure servers require the https:// protocol. The repository is created by a Jazz administrator, who must make it available on a local or network server.
  • A user ID and password for the repository. Team member credentials are created on the web server and in team areas by Jazz administrators. Your administrator can configure the repository for user authentication in an LDAP directory.
Smart Card authentication is available on Windows only. To enable Smart Card authentication, you must have the Microsoft Visual C++ 2010 redistributable package installed. You must then enable the IBM Common Access Card (CAC) provider within Java by editing the install-directory/TeamConcert/jdk/jre/conf/security/java.security file. Replace this section:
security.provider.1=SUN
security.provider.2=SunRsaSign
security.provider.3=SunEC
security.provider.4=SunJSSE
security.provider.5=SunJCE
security.provider.6=SunJGSS
security.provider.7=SunSASL
security.provider.8=XMLDSig
security.provider.9=SunPCSC
security.provider.10=JdkLDAP
security.provider.11=JdkSASL
security.provider.12=SunMSCAPI
security.provider.13=SunPKCS11
with this section:
security.provider.1=com.ibm.security.capi.IBMCAC
security.provider.2=com.ibm.jsse2.IBMJSSEProvider2
security.provider.3=com.ibm.crypto.provider.IBMJCE
security.provider.4=com.ibm.security.jgss.IBMJGSSProvider
security.provider.5=com.ibm.security.cert.IBMCertPath
security.provider.6=com.ibm.security.sasl.IBMSASL
security.provider.7=com.ibm.xml.crypto.IBMXMLCryptoProvider
security.provider.8=com.ibm.xml.enc.IBMXMLEncProvider
security.provider.9=org.apache.harmony.security.provider.PolicyProvider
security.provider.10=com.ibm.security.jgss.mech.spnego.IBMSPNEGO

About this task

To access the required views and controls, open the Work Items perspective. Click Window > Open Perspective > Other > Work Items.

Procedure

To create a connection to a repository:

  1. If you have not previously created a repository connection, click the Create a Repository Connection link in the Team Artifacts view. Otherwise, right-click in the Team Artifacts view and click New > Jazz Repository Connection.
  2. In Create a Jazz Repository Connection window, enter a Location URI. For example: https://hostname.example.com:9443/ccm.
    The Location Name defaults to the server host name. You can modify it to simplify or clarify the name.
  3. In the Authentication section, the default Authentication Type is Username and Password. Enter the user name and password that your Jazz administrator has provided for you. Alternatively, you can select Smart Card or SSL Certificate as Authentication Type.
  4. 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 java.security.krb5.realm, java.security.krb5.kdc, and java.security.krb5.conf system properties, respectively. For more information, see Engineering Lifecycle Management client configuration for Kerberos/SPNEGO SSO. 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.
  5. Optional: To log in using Windows credentials that are the same as the credentials that you use to access the Engineering Workflow Management 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.
  6. Click Finish.
    The repository connection is displayed in the Team Artifacts Repository Connections folder.
  7. To open a project area, right-click the repository connection in the Team Artifacts view and click Manage Connected Project Areas.
  8. Select one or more project areas and click Finish.