Do my 4.X client become unsupported the minute I upgrade my JTS to 6.0.3?
![](http://jazz.net/_images/myphoto/86eb906e18f6a98d68b7eb12c1e58cc1.jpg)
I know there’s N-1 support for client to server, but if we upgrade our JTS server to RTC 6.0.3, is that when 4.X clients would become in an unsupported mode? Or is it after we upgrade our CCM servers to RTC 6.0.3? The JTS does some level of authentication so I was wondering if that's when N-1 support comes into play. I'm asking, because I plan on upgrading our JTS one week, and our CCM servers the next. I'm trying to buy time for those straddlers needing to upgrade their clients to 5.0.2
Accepted answer
![](http://jazz.net/_images/myphoto/86eb906e18f6a98d68b7eb12c1e58cc1.jpg)
No 4.x client will be able to log into CCM one it is upgraded to 6.x.
No Client other than browsers log into JTS and the other applications and so there is no client compatibility.
Since you have to upgrade JTS first, there can be a time where JTS is at 6.x anf CCM is at 5.x.
Comments
![](http://jazz.net/_images/myphoto/86eb906e18f6a98d68b7eb12c1e58cc1.jpg)
Wouldn't a 4.X client have to authenticate and grab a license against the JTS before getting access to CCM artifacts? Not just from a browser.
![](http://jazz.net/_images/myphoto/e5e63d5878217b64611c1df9401b7cd3.jpg)
RTC clients only know the repository connection to CCM. Each application CCM, QM has their own authentication set up. JTS only handles the licenses for the other servers and even for that clients don't connect JTS.