Are the following teamserver.properties used in 6.0.x of CLM ?

Kevin Ramer (4.5k●8●178●197) | asked Dec 06 '16, 5:01 p.m.
edited Nov 05 '18, 12:30 p.m.

Hello,

We've been Jazz'ing since v2 and back in the day there was the need to imbed authentication data for certain teamserver.properties. Are the following still required :

com.ibm.rqm.buildintegration.userName
com.ibm.rqm.integrationprovider.userName
com.ibm.team.datawarehouse.BUILD_REMOTE_SNAPSHOT.remoteSnapshot.userid
com.ibm.team.datawarehouse.COMMON_REMOTE_SNAPSHOT.remoteSnapshot.userid
com.ibm.team.datawarehouse.SCM_REMOTE_SNAPSHOT.remoteSnapshot.userid
com.ibm.team.datawarehouse.WORKITEMS_REMOTE_SNAPSHOT.remoteSnapshot.userid
com.ibm.team.datawarehouse.auth.userId
com.ibm.rqm.buildintegration.userName
com.ibm.rqm.defects.userName
com.ibm.rqm.integrationprovider.userName
com.ibm.team.build.BuildResultPrunerTask.runAsUser
com.ibm.team.build.BuildSchedulerTask.runAsUser
com.ibm.team.datawarehouse.auth.userId

We have DCC enabled and all its connections use OAuth from DCC into the respective provider. I do recall changing QM build integration to use a 'qm_user' at the RTC side. The items with *REMOTE_SNAPSHOT" are in one of 20+ teamserver.properties whereas com.ibm.team.datawarehouse.auth.userId is common to all.

I ask because I just got a warning e-mail about weak password on non-expiring LDAP ID and want to try to catch all the places the credentials are located. If Jazz stuff doesn't use, that would allow me to safely ignore.

Any takers ?

Thanks !

One answer

Most liked answers ↑|Newest answers|Oldest answers

permanent link

Bharath Rao (885●30) | answered Jun 25 '21, 10:34 a.m.

Regarding the following datawarehouse related properties..

com.ibm.team.datawarehouse.BUILD_REMOTE_SNAPSHOT.remoteSnapshot.userid

com.ibm.team.datawarehouse.COMMON_REMOTE_SNAPSHOT.remoteSnapshot.userid

com.ibm.team.datawarehouse.SCM_REMOTE_SNAPSHOT.remoteSnapshot.userid

com.ibm.team.datawarehouse.WORKITEMS_REMOTE_SNAPSHOT.remoteSnapshot.userid

com.ibm.team.datawarehouse.auth.userId

These properties are not necessary. They are related to an old Java ETL replaced by DCC.

-----

Regarding the following QM buildintegration related properties..

com.ibm.rqm.buildintegration.userName

com.ibm.rqm.defects.userName

com.ibm.rqm.integrationprovider.userName

com.ibm.team.build.BuildResultPrunerTask.runAsUser

com.ibm.team.build.BuildSchedulerTask.runAsUser

For

com.ibm.rqm.defects.userName

>> Pre version 3.x, QM had the ability have 'local' defects. this has since been deprecated

we are assuming you do not have QM projects areas from 2.x that uses local defect anymore; if so this property is not needed..

For

com.ibm.team.build.BuildResultPrunerTask.runAsUser

com.ibm.team.build.BuildSchedulerTask.runAsUser

>> They are now both handled in the RTC advanced properties

They are now logged under Build Systems: com.ibm.team.build.internal.service.delete.BuildResultPrunerTask (the property names have changed post 2.x)

So, can be removed.

For

com.ibm.rqm.integrationprovider.userName

com.ibm.rqm.buildintegration.userName

>> These two were used when setting up integration with another application in the 2.x timeframe

Post 2.x they should not be needed given that you are integrating with CCM/RTC.

It's all about the answers!

Related questions

Are the following teamserver.properties used in 6.0.x of CLM ?

One answer

Your answer