Why does proxy auth on not work in RTC 3.0 eclipse client
Reverse proxy with authentication on is configured with RTC / Tomcat / LDAP. It works with RTC 2.0.x both for Web UI and for Eclipse client. The user authenticates on the Proxy and is redirected to RTC.
The same configuration works for RTC 3.0 Web UI. There is no problem. But the RTC eclipse client 3.0 throws error. Error in RTC 3.0 eclipse client when using proxy with authentication on: com.ibm.team.repository.client.ServerVersionCheckException: The server you are connecting to is older than your client and not compatible. Please contact your system administrator to determine the server version and download the appropriate client. at com.ibm.team.repository.client.internal.TeamRepository.checkServerVersionMatches(TeamRepository.java:1604) at com.ibm.team.repository.client.internal.TeamRepository.internalLogin(TeamRepository.java:1444) at com.ibm.team.repository.client.internal.TeamRepository.login(TeamRepository.java:617) at com.ibm.team.process.internal.rcp.ui.LoginAction$1.run(LoginAction.java:88) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) Caused by: com.ibm.team.repository.transport.client.AuthenticationException: CRJAZ0102I You must enter a user name and password. at com.ibm.team.repository.transport.client.ClientHttpUtil.throwEmptyCredsException(ClientHttpUtil.java:1295) What changes made in RTC 3.0 could cause this configuration not to work anymore? |
3 answers
Reverse proxy with authentication on is configured with RTC / Tomcat / LDAP. It works with RTC 2.0.x both for Web UI and for Eclipse client. The user authenticates on the Proxy and is redirected to RTC. Hi Elizabeth I have just encountered the same issue with a customer. The way to resolve it is to go the Windows > Preferences in the Eclipse client and then Network Connections. In the Active Provider window change from Native to Direct, apply and OK. In RTC V2 by default Direct was set, however in RTC V3 the setting by default is Native. Work item 141323 refers to the same issue. Also this post refers to the same issue: http://jazz.net/forums/viewtopic.php?t=14135&highlight=proxy+authentication Hope this helps Sally |
|
Thanks Sally for sharing. This option is already checked but not working.
Had your customer as well authentication ON on the Proxy? Did they use Tomcat as well? /Elisabeth |
Thanks Sally for sharing. This option is already checked but not working. Hi - no they are using WAS not tomcat. The WAS settings are set to: Global Security > Authenticate only when the URI is protected and Use available auth data when an unprotected URI is accessed. Also In GS, Application security is enabled. Thanks |
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.